Add kubeadm upgrade docs
#4770
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,54 @@ | ||
| --- | ||
| approvers: | ||
| - pipejakob | ||
|
There was a problem hiding this comment. and luxas ;) There was a problem hiding this comment. he he, a copy and paste thing, yes makes sense … |
||
| title: Upgrading kubeadm clusters | ||
| --- | ||
|
|
||
| {% capture overview %} | ||
|
|
||
| This guide is for upgrading kubeadm clusters from version 1.7.x to 1.8.x. | ||
| See also [upgrading kubeadm clusters from 1.6 to 1.7](/docs/tasks/administer-cluster/kubeadm-upgrade-1-7/) if you're on a 1.6 cluster, currently. | ||
|
|
||
| {% endcapture %} | ||
|
|
||
| {% capture prerequisites %} | ||
| You need to have a Kubernetes cluster running version 1.7.x in order to use the process described here. Note that only one minor version upgrade is supported, that is, you can only upgrade from, say 1.7 to 1.8, not from 1.7 to 1.9. | ||
|
There was a problem hiding this comment. nit: v1.7.0 or higher Maybe we can move the note down to the out-of-scope section? |
||
|
|
||
| Before proceeding, make sure you read the [release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG.md#v180-alpha2) carefully. | ||
|
|
||
| The following is out of scope for `kubeadm upgrade`, that is, you need to take care of it yourself: | ||
|
|
||
| - No etcd upgrades are performed. You can, for example, use `etcdctl` to take care of this. | ||
| - Any app-level state, for example, a database an app might depend on (like MySQL or MongoDB) must be backed up beforehand. | ||
|
There was a problem hiding this comment. Can we break this out to a section where you're saying the general: "As a best-practice; you should back up what's important to you" or something like that |
||
|
|
||
|
|
||
| Note that `kubeadm upgrade` is 'eventually idempotent', that is, you can run it over and over again if you find yourself in a bad state and it should be able to recover. | ||
|
There was a problem hiding this comment. Can you move this down to the recovery section? |
||
|
|
||
| {% endcapture %} | ||
|
|
||
| {% capture steps %} | ||
|
|
||
| ## On the master | ||
|
There was a problem hiding this comment. Can we name this Then remind the user that this has to be done on the master |
||
|
|
||
| 1. Upgrade `kubectl` using [curl](/docs/tasks/tools/install-kubectl/#install-kubectl-binary-via-curl). Note: DO NOT use `apt` or `yum` or any other package manager to upgrade it. | ||
|
There was a problem hiding this comment. only upgrading kubeadm manually is actually required. There was a problem hiding this comment. Hmmm, now I'm a bit confused. At least that was the state when we discussed it. Has this changed or did I misunderstand you here? There was a problem hiding this comment. This is unnecessary. Only kubeadm is needed |
||
|
|
||
| 2. Install the most recent version of `kubeadm` using curl. | ||
|
There was a problem hiding this comment. Please tell us how to do that: $ export VERSION=v1.8.0 # or any given released k8s version
$ export ARCH=amd64 # or arm, arm64, ppc64le or s390x
$ curl -sSL https://dl.k8s.io/release/${VERSION}/bin/linux/${ARCH}/kubeadm > /usr/bin/kubeadm |
||
|
|
||
| 3. On the master node, run `kubeadm upgrade plan`, which tells you what versions are available. | ||
|
There was a problem hiding this comment. Please add these in code blocks: and paste some preliminary output (I have that on the upgrades PR). Please explain what this command does as well, like:
|
||
|
|
||
| 4. Pick a version to upgrade to and run, for example, `kubeadm upgrade apply --version v1.7.3`. | ||
|
There was a problem hiding this comment. Add this in a code block as well so it's more discoverable; and with some simple outputs.
|
||
|
|
||
| 5. After `kubeadm upgrade` you need to manually upgrade your SDN. | ||
|
|
||
| Your CNI provider might have its own upgrade instructions to follow now. | ||
| Check the [addons](/docs/concepts/cluster-administration/addons/) page to | ||
| find your CNI provider and see if there are additional upgrade steps | ||
| necessary. | ||
|
|
||
| ## Recovering from a bad state | ||
|
|
||
| You can use `kubeadm upgrade` to change a running cluster with `x.x.x --> x.x.x` with `--force`, which can be used to recover from a bad state. | ||
|
There was a problem hiding this comment. nit: If |
||
|
|
||
| {% endcapture %} | ||
|
|
||
| {% include templates/task.md %} | ||
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.
Please revert the addition of the extra spacing.
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.
Oops, sorry, didn't notice this. It's due to an Atom package that automatically formats YAML files.