re-positioned drain/uncorden steps in kubeadm upgrade docs

This commit is contained in:
Sam Culley
2020-12-31 07:07:35 +00:00
parent 46fdf32635
commit 91cff33a6c
@@ -91,13 +91,6 @@ Find the latest stable 1.18 version:
kubeadm version kubeadm version
``` ```
- Drain the control plane node:
```shell
# replace <cp-node-name> with the name of your control plane node
kubectl drain <cp-node-name> --ignore-daemonsets
```
- On the control plane node, run: - On the control plane node, run:
```shell ```shell
@@ -244,13 +237,6 @@ For more information see the [certificate management guide](/docs/tasks/administ
This step is not required on additional control plane nodes if the CNI provider runs as a DaemonSet. This step is not required on additional control plane nodes if the CNI provider runs as a DaemonSet.
- Uncordon the control plane node:
```shell
# replace <cp-node-name> with the name of your control plane node
kubectl uncordon <cp-node-name>
```
### Upgrade additional control plane nodes ### Upgrade additional control plane nodes
Same as the first control plane node but use: Same as the first control plane node but use:
@@ -267,6 +253,15 @@ sudo kubeadm upgrade apply
Also `sudo kubeadm upgrade plan` is not needed. Also `sudo kubeadm upgrade plan` is not needed.
### Drain the control plane node
- Prepare the node for maintenance by marking it unschedulable and evicting the workloads:
```shell
# replace <cp-node-name> with the name of your control plane node
kubectl drain <cp-node-name> --ignore-daemonsets
```
### Upgrade kubelet and kubectl ### Upgrade kubelet and kubectl
Upgrade the kubelet and kubectl on all control plane nodes: Upgrade the kubelet and kubectl on all control plane nodes:
@@ -295,6 +290,15 @@ sudo systemctl daemon-reload
sudo systemctl restart kubelet sudo systemctl restart kubelet
``` ```
### Uncordon the control plane node
- Bring the node back online by marking it schedulable:
```shell
# replace <cp-node-name> with the name of your control plane node
kubectl uncordon <cp-node-name>
```
## Upgrade worker nodes ## Upgrade worker nodes
The upgrade procedure on worker nodes should be executed one node at a time or few nodes at a time, The upgrade procedure on worker nodes should be executed one node at a time or few nodes at a time,
@@ -321,6 +325,14 @@ without compromising the minimum required capacity for running your workloads.
{{% /tab %}} {{% /tab %}}
{{< /tabs >}} {{< /tabs >}}
### Upgrade the kubelet configuration
- Call the following command:
```shell
sudo kubeadm upgrade node
```
### Drain the node ### Drain the node
- Prepare the node for maintenance by marking it unschedulable and evicting the workloads: - Prepare the node for maintenance by marking it unschedulable and evicting the workloads:
@@ -338,14 +350,6 @@ without compromising the minimum required capacity for running your workloads.
node/ip-172-31-85-18 drained node/ip-172-31-85-18 drained
``` ```
### Upgrade the kubelet configuration
- Call the following command:
```shell
sudo kubeadm upgrade node
```
### Upgrade kubelet and kubectl ### Upgrade kubelet and kubectl
- Upgrade the kubelet and kubectl on all worker nodes: - Upgrade the kubelet and kubectl on all worker nodes: