-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Use the OnDelete updateStrategy for AWS VPC CNI DaemonSet #11590
Conversation
I don't recall, will nodes that have outdated daemonset pods report as needing update in |
@rifelpet not unless something changes in the node's userdata. |
You can set UpdateNeeded on the addon manifest in bootstrapchannelbuilder. See how cilium does it. |
19d46a4
to
6ac345e
Compare
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olemarkus The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@johngmyers I think it should be cherry-picked to 1.20 too. |
…1590-upstream-release-1.21 Automated cherry pick of #11590: Use the OnDelete updateStrategy for AWS VPC CNI DaemonSet
@hakman feel free to propose a cherry-pick. |
…-upstream-release-1.20 Automated cherry pick of #11590: Use the OnDelete updateStrategy for AWS VPC CNI DaemonSet
Any chance to get this backported to 1.19? For now our migration to 1.20 is blocked |
At the moment, there is no plan for a new 1.19 release. |
But you don't have to upgrade to kops minor version by minor version. So once this is released in 1.20 (I believe we don't have a patch version with this change in it) then you can use kops 1.20 directly. |
Fixes #11589