-
Notifications
You must be signed in to change notification settings - Fork 21
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
fix: force redownload of Kubelet and kubectl binaries for Flatcar #889
Conversation
Without this fix, upgraded Nodes ended up not actually upgrade the Kubelet version
Tested manually by using a dev image to run a pre-provisioned Kubernetes cluster upgrade (note the
|
@@ -57,6 +57,7 @@ | |||
mode: 0755 | |||
owner: root | |||
group: root | |||
force: true |
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.
very interesting catch for preprovisioned case. I think we have to scan the KIB code to make sure we fix similar issues with other binaries.
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.
Yep I looked at that, this PR was actually a followup to https://d2iq.atlassian.net/browse/D2IQ-95908, we just missed it the first time :(
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.
Thank you.
Without this fix, upgraded Nodes ended up not actually upgrade the Kubelet version
What problem does this PR solve?:
Force redownload the Kubelet and kubectl binaries for Flatcar.
Without this fix, upgraded Nodes ended up not actually upgrading the Kubelet version.
Which issue(s) does this PR fix?:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: