-
Notifications
You must be signed in to change notification settings - Fork 3.4k
v1.7 backports 2020-05-08 #11441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.7 backports 2020-05-08 #11441
Conversation
[ upstream commit 942b8bd ] Signed-off-by: Tobias Klauser <tklauser@distanz.ch> Signed-off-by: Chris Tarazi <chris@isovalent.com>
…y checks that expect an L3 deny [ upstream commit 0bbb6c2 ] Signed-off-by: Dan Wendlandt <dan@covalent.io> Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit 3fe0838 ] Signed-off-by: Dan Wendlandt <dan@covalent.io> Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit 6bcbf2d ] Signed-off-by: Dan Wendlandt <dan@covalent.io> Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit 4b865d5 ] This PR fixes the kubectl create option that was missing at some places in the update.rst file. Signed-off-by: Swaminathan Vasudevan <svasudevan@suse.com> Signed-off-by: Chris Tarazi <chris@isovalent.com>
never-tell-me-the-odds |
@aanm Could you please take a look at the PRs of yours that had non-trivial conflicts? |
@qmonnet Could you please take a look at the PR of yours that did not apply cleanly? |
[ upstream commit 90712d1 ] Users are getting confused by this language, trying to figure out if there is a technical reason behind this statement. This PR tries to clarify that there is no technical reason. Signed-off-by: Sergey Generalov <sergey@isovalent.com> Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit 9019f8a ] Reduce logging verbosity by not printing the whole 'Node' in the log messages. Do not initialize deprecated build version field in the 'Node' in bootstrap. Signed-off-by: Jarno Rajahalme <jarno@covalent.io> Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit 6d364cd ] Signed-off-by: Sean Winn <sean@isovalent.com> Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit 048a528 ] Currently, this facility doesn't exist in the upstream netlink library (https://github.com/vishvananda/netlink). This commit adds it here so that we don't have to wait to utilize it when it's merged. Once it's merged, then we can replace this. Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit 06c00c1 ] This makes log messages containing the rule much easier to read when debugging. Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit ac50a4b ] Previously, ENI rules were created, but never cleaned up. This can result in an increasing number of stale rules over the lifetime of a node. This commit adds the ability to delete these rules (ingress and egress). Note that routes are deliberately not deleted as they can be reused for future endpoints on the same node. This is due to the routes being created with the ENI device "ifindex" as the table ID. Fixes #11041 Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit 83fc45a ] Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit 820d852 ] Previously, we relied on a log message to indicate whether a deletion of a rule failed. Relying on the log message can be potentially misleading as endpoint deletion is best-effort and errors are ignored in the end. The user may see log message indicating a rule was deleted, but later in the endpoint deletion it would show as an error. This commit changes the function which deletes rules to surface the error. This change removes the misleading log messages and allows us to assert against this in tests. Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit b58dd14 ] This commit structures the code in such a way that allows the previously duplicated parsing/validation logic to be consolidated into one place. It also reduces the interdependencies between packages and allows for a dummy implementation to be used for testing purposes. Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit a83d538 ] Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit 410385a ] There are missing "break" keywords in the switch statement to process the different ICMPv6 message types. Let's add them. Indirectly reported by cppcheck which would complain that icmp4.code would be overwritten before being read (which happens indeed if we fall through). Fixes: f7396ba ("Add support for nat46 icmp translation.") Signed-off-by: Quentin Monnet <quentin@isovalent.com> Signed-off-by: Chris Tarazi <chris@isovalent.com>
414b71f
to
aa4b746
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good for the commit I did in #11410 and discussed above, thank you 👍
…etup [ upstream commit 1dfe49f ] This avoids having to bump the Go version in the docs manually and also allows to get rid of the Go version check in Documentation/Makefile. Signed-off-by: Tobias Klauser <tklauser@distanz.ch> Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit c95f93b ] Read the Go version from the GO_VERSION file and use it to replace the hard-coded versions in the test scripts. Together with the preceding commits, this allows to bump the Go version in a single place: the GO_VERSION file. Updating to a new Go version (1.13.8 in this example) is now as easy as: echo 1.13.8 > GO_VERSION && make update-golang Signed-off-by: Tobias Klauser <tklauser@distanz.ch> Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit 78739a1 ] Signed-off-by: John Watson <johnw@planetscale.com> Signed-off-by: Chris Tarazi <chris@isovalent.com>
never-tell-me-the-odds |
restart-ginkgo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
With regard to the failed backport of #11269, I left a comment about it here: #11269 (comment)
But let's do that in the next batch of backports, this PR is already large enough as is.
Dropping this commit will lead to inconsistencies when bumping Go version on the I noted that If there is no strong reason against it, I'd propose to pick up 771aa8a in this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving despite one minor issue wrt. Go version update due to the dropped commit as pointed out in #11441 (comment) Hopefully we can address this in a future backport PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed ENI related backports |
[ upstream commit 7dd2b36 ] This will allow to easily bump the version via a Makefile target introduced in a successive commit. Signed-off-by: Tobias Klauser <tklauser@distanz.ch> Signed-off-by: Chris Tarazi <chris@isovalent.com>
@tklauser Thanks for clearing that up! I've re-added the commit and ran the |
never-tell-me-the-odds Edit: provisioning failure |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks.
test-upstream-k8s Edit: hit #10442 |
test-missed-k8s |
test-missed-k8s |
1 similar comment
test-missed-k8s |
Note: Dropped 771aa8a as it wasn't needed for backporting; no functionality or behavior is lostmake update-golang
as wellSkipping due to non-trivial conflicts:
Causing build failures:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/3083/testReport/junit/Suite-k8s-1/12/K8sChaosTest_Connectivity_demo_application_Endpoint_can_still_connect_while_Cilium_is_not_running/
Once this PR is merged, you can update the PR labels via: