-
Notifications
You must be signed in to change notification settings - Fork 3.4k
v1.11 backports 2022-10-19 #21810
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.11 backports 2022-10-19 #21810
Conversation
[ upstream commit 694892c ] CCNPs are converted internally into CNPs, but metadata.name has been forgotten Fixes #21393 [ Backport note: File operator/cilium_node.go has been renamed into operator/cmd/cilium_node.go in master branch. ] Signed-off-by: Andrey Klimentyev <andrey.klimentyev@flant.com> Signed-off-by: Quentin Monnet <quentin@isovalent.com>
[ upstream commit 6fbbbb9 ] Add some additional notes to highlight how Cilium's k8s NetworkPolicy support works, including: - Egress policies have not been beta for several years. - Port Ranges. [ Backport note: File Documentation/network/kubernetes/policy.rst has been renamed into Documentation/concepts/kubernetes/policy.rst on master branch. ] Signed-off-by: Joe Stringer <joe@cilium.io> Signed-off-by: Quentin Monnet <quentin@isovalent.com>
[ upstream commit 061e55f ] In high-churn clusters, there can be a three-party deadlock between the EndpointManager, the PolicyRepository, and a given Endpoint. One of the "links in the chain" is merely trying to get the container ID and namespace+name of an Endpoint for logging. Which we already have. So, rather than trying to lock an Endpoint to get it's identifiers again, just use the copy we already have. Fixes: dae07b5 (endpointmanager: Remove goroutine for ID release) Signed-off-by: Casey Callendrello <cdc@isovalent.com> Signed-off-by: Quentin Monnet <quentin@isovalent.com>
be31bfc
to
9219f14
Compare
/test-backport-1.11 Job 'Cilium-PR-K8s-1.19-kernel-4.9' failed: Click to show.Test Name
Failure Output
If it is a flake and a GitHub issue doesn't already exist to track it, comment Job 'Cilium-PR-K8s-GKE' failed: Click to show.Test Name
Failure Output
If it is a flake and a GitHub issue doesn't already exist to track it, comment Job 'Cilium-PR-K8s-GKE' failed: Click to show.Test Name
Failure Output
If it is a flake and a GitHub issue doesn't already exist to track it, comment |
/test-1.19-4.9 |
/test-gke |
/ci-aks-1.11 |
/ci-gke-1.11 |
/test-gke |
/ci-gke-1.11 |
/ci-aks-1.11 |
This issue I don't like: https://jenkins.cilium.io/job/Cilium-PR-K8s-GKE/9168/testReport/junit/Suite-k8s-1/22/K8sDatapathConfig_IPv4Only_Check_connectivity_with_IPv6_disabled/
Seems like it was it hit before hand as well? Is it consistent? I'll re-run to check. In any case the GKE pipeline is very flaky and disabled on |
/test-gke |
Looks like it happened again
Although on a different test |
/test-gke |
/ci-aks-1.11 |
/test-gke |
I filed a flake for the error we observed earlier on GKE. Last run seems to have failed very early, likely on infra issue. GKE pipeline being very unstable and not required, and AKS being unstable too, I believe this PR is good to go? |
PRs skipped due conflicts:
Once this PR is merged, you can update the PR labels via:
or with