-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
kubeadm: component config updates in 1.19 #21663
kubeadm: component config updates in 1.19 #21663
Conversation
Deploy preview for kubernetes-io-vnext-staging processing. Building with commit 65e914e https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/5f0f05a9fff5710008bbd0fe |
/milestone 1.19 |
93ded8c
to
d18fa51
Compare
{{< note >}} | ||
If `kubeadm upgrade plan` shows any component configs that require manual upgrade, users must provide | ||
a config file with replacement configs to `kubeadm upgrade apply` via the `--config` command line flag. | ||
Failing to do so will cause `kubeadm upgrade apply` to exit with an error and not perform an upgrade. |
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.
My idea here is for this note to also contain a link at the end to a different page describing in detail the workflow in that case. For that matter, however, we should have the alpha commands from the KEP merged as well (possibly in the next release cycle).
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.
My idea here is for this note to also contain a link at the end to a different page describing in detail the workflow in that case.
if the new page is going to be at k/website it's fine because the k8s.io docs are branched.
if it links at k/kubeadm, the repo is not branched, so we better have SHAs in the link.
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.
I am thinking more about using k/website for that. That's why I want the full set of command line additions to merge before doing the separate page.
@rosti thanks! |
It seems that it only requires version bumps here and there. I can do that in this PR (as a separate commit). Will update later today. |
|
||
To see information about upgrading clusters created using older versions of kubeadm, | ||
please refer to following pages instead: | ||
|
||
- [Upgrading kubeadm cluster from 1.17 to 1.18](https://v1-18.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) | ||
- [Upgrading kubeadm cluster from 1.16 to 1.17](https://v1-17.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) | ||
- [Upgrading kubeadm cluster from 1.15 to 1.16](https://v1-16.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) | ||
- [Upgrading kubeadm cluster from 1.14 to 1.15](https://v1-15.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-15/) |
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.
@neolit123 should we drop the link "from 1.14 to 1.15"?
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.
If v1.14 is still supported after the v1.19 release happens, I would expect to leave that link in.
Added the generic 1.19 updates to this PR too (as a separate commit). |
@rosti the PR description reads
Is that still accurate? |
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.
|
||
To see information about upgrading clusters created using older versions of kubeadm, | ||
please refer to following pages instead: | ||
|
||
- [Upgrading kubeadm cluster from 1.17 to 1.18](https://v1-18.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) | ||
- [Upgrading kubeadm cluster from 1.16 to 1.17](https://v1-17.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) | ||
- [Upgrading kubeadm cluster from 1.15 to 1.16](https://v1-16.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) | ||
- [Upgrading kubeadm cluster from 1.14 to 1.15](https://v1-15.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-15/) |
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.
If v1.14 is still supported after the v1.19 release happens, I would expect to leave that link in.
/hold OK to unhold once this is rebased. |
This briefly adds a description for some side steps in the upgrade process. Most notably, it mentions the existance of the component config state table at the end of the `kubeadm upgrade plan` output and the need to specify a file with upgraded configs to `kubeadm upgrade apply` if the config state table says so. Signed-off-by: Rostislav M. Georgiev <rostislavg@vmware.com>
Signed-off-by: Rostislav M. Georgiev <rostislavg@vmware.com>
1367ba3
to
65e914e
Compare
@sftim rebased it. @fabriziopandini PTAL |
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.
@rosti thanks for taking care of this work!
/approve
/lgtm
|
||
To see information about upgrading clusters created using older versions of kubeadm, | ||
please refer to following pages instead: | ||
|
||
- [Upgrading kubeadm cluster from 1.17 to 1.18](https://v1-18.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) |
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.
@rosti , Would you check the last two links. Are both links required? The links point to the 1.15 snapshot version of the docs.
1.18-1.19
1.17-1.18
1.16-1.17
1.15-1.1.6
1.14-1.15 ?
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.
The idea there is to keep as much as possible from the older upgrade docs to allow folks with older clusters to incrementally upgrade to modern Kubernetes versions.
These are good to be kept as long as the 1.15 snapshot is still present. If not, I can send a PR to remove the link.
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.
OK.
Hi @rosti . Besides checking on the links to previous upgrade instructions, the page looks good. |
Besides the link question, |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini, kbhawkey 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 |
This is a placeholder for now./assign @neolit123 @fabriziopandini
/sig cluster-lifecycle