From 3a13717a3494a7e30fa88db81c5a4fe3b4116070 Mon Sep 17 00:00:00 2001 From: Aditya Samant Date: Wed, 13 Dec 2023 16:16:31 +0530 Subject: [PATCH] Issue 44321 - added comments to emphasize that the drain and uncordon commands must be executed on a control plane node. Apply suggestions from code review Co-authored-by: Lubomir I. Ivanov --- .../tasks/administer-cluster/kubeadm/upgrading-linux-nodes.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/docs/tasks/administer-cluster/kubeadm/upgrading-linux-nodes.md b/content/en/docs/tasks/administer-cluster/kubeadm/upgrading-linux-nodes.md index 7fd2738ca5102..e61c6f3d2b134 100644 --- a/content/en/docs/tasks/administer-cluster/kubeadm/upgrading-linux-nodes.md +++ b/content/en/docs/tasks/administer-cluster/kubeadm/upgrading-linux-nodes.md @@ -62,6 +62,7 @@ sudo kubeadm upgrade node Prepare the node for maintenance by marking it unschedulable and evicting the workloads: ```shell +# execute this command on a control plane node # replace with the name of your node you are draining kubectl drain --ignore-daemonsets ``` @@ -99,6 +100,7 @@ kubectl drain --ignore-daemonsets Bring the node back online by marking it schedulable: ```shell +# execute this command on a control plane node # replace with the name of your node kubectl uncordon ```