-
Notifications
You must be signed in to change notification settings - Fork 42.2k
bump cni library version to v0.8.0 #91896
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
|
/assign @BenTheElder @liggitt @dims |
|
@aojea let's please ask them to tag 0.7.2 for us to use. /hold |
|
poke to cni maintainer to see if they can tag a new release |
Opening an issue in the CNI repo would be a good way to do that. I believe it would be 0.8.0 due to a (minor) interface change. |
last CNI library release is 0.7.1 from Jun 11, 2019. Since then, there was introduced new feature and bugfixes. Currently, this library is only being used by dockershim, the other CRI plugins are vendoring it directly However, this will help also to mitigate some of the issues with the CI jobs that are still using dockershim. Signed-off-by: Antonio Ojea <[email protected]>
|
/retest @liggitt this looks ready! |
| // If the plugin is currently about to be written, then we wait a | ||
| // second and try it again | ||
| if strings.Contains(err.Error(), "text file busy") { | ||
| time.Sleep(time.Second) | ||
| continue | ||
| } |
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.
is there a path in kube that hits this?
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.
@saschagrunert you've added this containernetworking/cni#763,
can you help me to answer this question 😄 ?
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.
There was a setup race where the init container downloads the CNI Plugin binary (like Cilium) and the runtime immediately picks up the (not finished copying) executable on disk. This caused issues in multiple distributions on cluster bootstrap, so we added this feature of retrying.
I don’t think that CNI invocations happen directly via Kubernetes, usually the runtime does this (last famous words).
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea, liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
saschagrunert
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.
/lgtm
|
/hold cancel |
What type of PR is this?
/kind feature
/kind flake
What this PR does / why we need it:
last CNI library release is 0.7.1 from Jun 11, 2019.
Since then, there was introduced new feature and bugfixes.
Currently, this library is only being used by dockershim,
the other CRI plugins are vendoring it directly
However, this will help also to mitigate some of the issues with the
CI jobs that are still using dockershim.
Specially interesting the new cache feature and some bugfixes to improve
resilience to errors.
Signed-off-by: Antonio Ojea [email protected]
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: