whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated document commands to use placeholders. Incorporated feedback. (#18208)

Browse Source
This commit is contained in:
Sharjeel Aziz
2020-01-15 04:19:32 -05:00
committed by Kubernetes Prow Robot
parent d2dc2c60c6
commit 69ceca708e
1 changed files with 11 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md
+11 -7
View File
@@ -91,7 +91,8 @@ The upgrade workflow at high level is the following:
1. Drain the control plane node: 1. Drain the control plane node:
```shell ```shell
kubectl drain $CP_NODE --ignore-daemonsets # replace <cp-node-name> with the name of your control plane node
kubectl drain <cp-node-name> --ignore-daemonsets
``` ```
1. On the control plane node, run: 1. On the control plane node, run:
@@ -144,10 +145,10 @@ The upgrade workflow at high level is the following:
1. Choose a version to upgrade to, and run the appropriate command. For example: 1. Choose a version to upgrade to, and run the appropriate command. For example:
```shell ```shell
# replace x with the patch version you picked for this upgrade
sudo kubeadm upgrade apply v1.17.x sudo kubeadm upgrade apply v1.17.x
``` ```
- Replace `x` with the patch version you picked for this upgrade.
You should see output similar to this: You should see output similar to this:
@@ -237,10 +238,11 @@ The upgrade workflow at high level is the following:
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.
1. Uncordon the control plane node 1. Uncordon the control plane node:
```shell ```shell
kubectl uncordon $CP_NODE # 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
@@ -306,10 +308,11 @@ without compromising the minimum required capacity for running your workloads.
### Drain the node ### Drain the node
1. Prepare the node for maintenance by marking it unschedulable and evicting the workloads. Run: 1. Prepare the node for maintenance by marking it unschedulable and evicting the workloads:
```shell ```shell
kubectl drain $NODE --ignore-daemonsets # replace <node-to-drain> with the name of your node you are draining
kubectl drain <node-to-drain> --ignore-daemonsets
``` ```
You should see output similar to this: You should see output similar to this:
@@ -356,7 +359,8 @@ without compromising the minimum required capacity for running your workloads.
1. Bring the node back online by marking it schedulable: 1. Bring the node back online by marking it schedulable:
```shell ```shell
kubectl uncordon $NODE # replace <node-to-drain> with the name of your node
kubectl uncordon <node-to-drain>
``` ```
## Verify the status of the cluster ## Verify the status of the cluster