-
Notifications
You must be signed in to change notification settings - Fork 3.8k
[release/1.7] script/setup/install-cni: install CNI plugins v1.9.0 #12660
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
Conversation
|
This is a huge change. Updates to hcsshim, grpc, otel often lead to issues directly in this repo or in downstreams importers. Downstreams importers should mostly be moved to 2.0 already, but this is still an unexpected change for a stable 30th patch release. Could we just update the package binaries instead? It seems we should be able to do that by adding a flag in the Makefile to call to install cni. Could updated binaries have issue with the large version difference? (1.2 to 1.9). |
mikebrow
left a 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.
see comment on hcshim version and question about go-cni
30a3e40 to
4d8b2ff
Compare
done |
4d8b2ff to
e1c73d5
Compare
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
e1c73d5 to
7db16b5
Compare
|
Just FYI, needed to add this: kubernetes-sigs/cri-tools#1961 since install-cni changed arguments |
For CVE-2025-67499
In containerd v1.7, the CNI plugin binaries are included in the
cri-cni-containerd-*-linux-*.tar.gzbundle.