-
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
Update some wording on kubeadm upgrades #4272
Conversation
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.
One small suggestion for one of the sentences.
@@ -57,6 +57,10 @@ You need to have a Kubernetes cluster running version 1.6.x. | |||
|
|||
4. Perform kubeadm upgrade. | |||
|
|||
**WARNING**: All parameters you passed to the first `kubeadm init` when you bootstrapped your | |||
cluster **MUST** be specified here in the upgrade-`kubeadm init`-command. This is a limitation |
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.
suggested edit: "This is a limitation we plan to address in v1.8."
I think this is small enough to add Tech Review LGTM actually. I'll address the docs comment |
e9c629b
to
5f52c69
Compare
@chenopis Reasonable to merge now in order to fix issues like kubernetes/kubeadm#333 ASAP? |
Thanks! |
No prob. =) |
Fixes cases like: kubernetes/kubeadm#333
/cc @jbeda @pipejakob @timothysc @lukemarsden @chenopis
This change is