-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Update CNI to 1.2.0 #23320
Update CNI to 1.2.0 #23320
Conversation
/test-backport-1.12 |
[ upstream commit a1046bc ] Run `images/scripts/update-cni-version.sh 1.2.0` to update the CNI version. Ref: https://github.com/containernetworking/plugins/releases/tag/v1.2.0 Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
9b8b53c
to
3256c09
Compare
Signed-off-by: Cilium Imagebot <noreply@cilium.io>
/test-backport-1.12 Job 'Cilium-PR-K8s-1.17-kernel-4.9' hit: #23264 (98.50% similarity) Job 'Cilium-PR-K8s-1.20-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 |
test-1.17-4.9: a known flake: #22474 |
/test-1.17-4.9 |
k8s-1.20-kernel-4.9 hit several failures: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.20-kernel-4.9/1554/ All of these failures seem to point to a sudden loss of DNS. Given that none of the other workflows exhibited this issue, I presume it must either be a problem with the connectivity in the VM when it ran, or otherwise some sort of transient test issue. |
/test-1.20-4.9 |
/mlh new-flake Cilium-PR-K8s-1.20-kernel-4.9 👍 created #23369 |
/test-1.20-4.9 |
[ upstream commit a1046bc ]
Run
images/scripts/update-cni-version.sh 1.2.0
to update the CNI version.Ref: https://github.com/containernetworking/plugins/releases/tag/v1.2.0
Signed-off-by: Michi Mutsuzaki michi@isovalent.com