-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Upgrading kubeadm clusters - version notes out of date #44674
Comments
/language en |
Page related to the issue: https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/ |
it's kubelet versions to be precise, but kubeadm has no way to catch and verify what version of the kubelet the user deployed today. as can be seen in the doc here: that's a bit of a design problem... there were some AIs and some discussion here: we currently have e2e tests that verify the kubeadm vs kubelet skew, but there are some gotchas around kubelet flags. perhaps we can say something like this in a small note near the top:
|
/sig cluster-lifecycle |
/triage accepted |
/assign @pegasas |
PR merge. |
@pegasas: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Now that this has merged:
kubernetes/kubernetes#120825
The documentation needs to be upgraded to let folks know node versions can be behind more then 1.
The text was updated successfully, but these errors were encountered: