-
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
[v1.13] Update CNI to 1.3.0 #25454
[v1.13] Update CNI to 1.3.0 #25454
Conversation
Run `images/scripts/update-cni-version.sh 1.3.0` to update the CNI version. Ref: https://github.com/containernetworking/plugins/releases/tag/v1.3.0 Signed-off-by: Yongkun Gui <ygui@google.com>
Signed-off-by: Tim Horner <timothy.horner@isovalent.com>
/test-backport-1.13 |
When doing manual backports of PRs, please follow https://docs.cilium.io/en/v1.13/contributing/release/backports/#via-github-web-interface - this ensures that the release notes properly pick up the related changes. |
I've approved the base images build. |
@thorn3r The CI trigger doesn't seem like it has taken effect, I don't see the |
/test-backport-1.13 |
@joestringer trying again 🤞 |
That's weird, the GitHub action based workflows seemed to trigger, but the jenkins+ginkgo ones did not. |
/test-backport-1.13 Job 'Cilium-PR-K8s-1.25-kernel-4.19' hit: #25255 (88.79% similarity) Job 'Cilium-PR-K8s-1.20-kernel-4.19' failed: Click to show.Test Name
Failure Output
Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.20-kernel-4.19/1937/ If it is a flake and a GitHub issue doesn't already exist to track it, comment Then please upload the Jenkins artifacts to that issue. |
They triggered when I ran it, so there must be something about your user that's not configured right in the Cilium CI systems. Worth following up with the testing folks to find out why that's the case. You're an org member (part of the |
/ci-gke-1.13 |
/test-1.16-4.19 |
/test-1.25-4.19 |
k8s-1.25-kernel-4.19 (test-1.25-4.19) looks related to this flake: K8sVerifier Runs the kernel verifier against Cilium's BPF datapath. re-running |
/test-1.25-4.19 |
failure for k8s-1.25-kernel-4.19 (test-1.25-4.19) looks like it could be related to #22749 |
/test-1.20-4.19 |
/test-1.25-4.19 |
v1.13 backports 2023-05-12
Once this PR is merged, you can update the PR labels via: