-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
images: bump cni plugins to v1.5.0 #32629
Conversation
The result of running ``` images/scripts/update-cni-version.sh 1.5.0 ``` Signed-off-by: Anton Ippolitov <anton.ippolitov@datadoghq.com>
I think I also need to update the actual images like it was done here: #31347 Edit: nvm, found the docs here https://docs.cilium.io/en/latest/contributing/development/images/#update-cilium-builder-and-cilium-runtime-images |
@antonipp it looks like the second commit |
291b77d
to
10cf348
Compare
Yes, sorry, just fixed it! |
/test |
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.
Thanks @antonipp!
@antonipp it looks like there's still something off with the image hashes and |
Signed-off-by: Anton Ippolitov <anton.ippolitov@datadoghq.com>
Head branch was pushed to by a user without write access
The
cilium-runtime
image can no longer be built onmain
because the CNI plugin binaries for v1.4.1 were updated in-place: containernetworking/plugins#1038The SHAs on
main
are:cilium/images/runtime/cni-version.sh
Lines 4 to 5 in db5fcdc
and the new SHAs upstream are now:
I suggest that we no longer use 1.4.1 and we move towards 1.5.0 which was released properly yesterday. The changelog is very minimal so the bump should be relatively safe: https://github.com/containernetworking/plugins/releases/tag/v1.5.0