-
Notifications
You must be signed in to change notification settings - Fork 3.4k
v1.9 backports 2021-09-14 #17390
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.9 backports 2021-09-14 #17390
Conversation
Please take a close look at the patches, there was conflict with almost everyone of them. @pchaigno @jrajahalme can you also look at the commits from #17115 please? See this discussion for context. |
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.
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.
test/runtime: Look into log errors after test start #17351
LGTM
fbd1dcc
to
d9e17b1
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.
test-backport-1.9 |
I'll defer to @jrajahalme as I'm unsure the solution I proposed in that discussion is the right one. |
@jrajahalme added #17445 to the backport, but we previously had failures on k8s >=v1.17 that still need a look. |
test-backport-1.9 Job 'Cilium-PR-K8s-1.17-kernel-4.9' failed and has not been observed before, so may be related to your PR: Click to show.Test Name
Failure Output
If it is a flake, comment Job 'Cilium-PR-K8s-1.18-kernel-4.19' failed and has not been observed before, so may be related to your PR: Click to show.Test Name
Failure Output
If it is a flake, comment |
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.
policy: Fix transient policy deny during agent restart #17115 (@jaffcheng)
LGTM
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.
Istio changes look good :-)
test-backport-1.9 |
Maybe spoke too soon, this may still need to be included: |
2c1253c
to
22d0726
Compare
@jrajahalme added #14704 to the backports, please re-review both #14704 #17275 patches as there were conflicts (although trivial). |
This is also needed, even though the backport-done label is already on, must be due to a mistake of mine: |
22d0726
to
13371b6
Compare
[ upstream commit 2423a0c ] Update Istio integration to Istio release 1.7.6. Istioctl CLI syntax has changed slightly, instead of `cilium-istioctl manifest apply -y` we now use `cilium-istioctl install -y`. Signed-off-by: Jarno Rajahalme <jarno@covalent.io> Signed-off-by: Alexandre Perrin <alex@kaworu.ch>
Done |
[ upstream commit ee18c90 ] Update Istio integration to Istio release 1.8.2. Istioctl no longer lists the service name for an inbound port. Signed-off-by: Jarno Rajahalme <jarno@covalent.io> Signed-off-by: Alexandre Perrin <alex@kaworu.ch>
[ upstream commit 4c87394 ] Update Cilium Istio integration to Istio release 1.10.4. Signed-off-by: Jarno Rajahalme <jarno@isovalent.com> Signed-off-by: Alexandre Perrin <alex@kaworu.ch>
[ upstream commit 3992048 ] Istio 1.10 requires at least k8s version 1.17. Signed-off-by: Jarno Rajahalme <jarno@isovalent.com> Signed-off-by: Alexandre Perrin <alex@kaworu.ch>
[ upstream commit 38994b0 ] When running runtime tests locally sometimes the test fail as level=error log entries are found that are the result of cilium-agent restarts during provisioning. This is similar to the fix done in cilium#14529. Signed-off-by: Jussi Maki <jussi@isovalent.com> Signed-off-by: Alexandre Perrin <alex@kaworu.ch>
[ upstream commit 55bfba9 ] Signed-off-by: Martynas Pumputis <m@lambda.lt> Signed-off-by: Alexandre Perrin <alex@kaworu.ch>
[ upstream commit 6418ade ] This pulls in a few fixes around ioctl wrappers wrt. unsafe.Pointer usage and fixes ifreqEthtool to be correctly padded. Ref. golang/sys@e5e7981 Ref. golang/sys@b450225 Signed-off-by: Tobias Klauser <tobias@cilium.io> Signed-off-by: Alexandre Perrin <alex@kaworu.ch>
[ upstream commit d82ac6f ] Use the ioctl wrapper provided in the golang.org/x/sys/unix package with the correctly padded ifreqData struct, rather than providing our own wrapper and struct which is incorrectly padded. Also add a simple unit test and make sure the package is only built on Linux. Signed-off-by: Tobias Klauser <tobias@cilium.io> Signed-off-by: Alexandre Perrin <alex@kaworu.ch>
[ upstream commit e0da2e4 ] Signed-off-by: Tom Payne <tom@isovalent.com> Co-authored-by: Nicolas Busseneau <nicolas@isovalent.com> Signed-off-by: Alexandre Perrin <alex@kaworu.ch>
/test-backport-1.9 Job 'Cilium-PR-K8s-1.17-kernel-5.4' failed and has not been observed before, so may be related to your PR: Click to show.Test Name
Failure Output
If it is a flake, comment |
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.
Istio backports seem complete now! Hoping the test will pass..
@pchaigno @nbusseneau seems to me that |
Once this PR is merged, you can update the PR labels via: