From b00ffa20936e4888850e10e0941bdc4a8209298b Mon Sep 17 00:00:00 2001 From: "Lubomir I. Ivanov" Date: Thu, 13 Jan 2022 15:17:26 +0200 Subject: [PATCH] kubeadm-upgrade: adjust note about node drain The current entry under additional information about drain can be confusing and users might jump into draining the nodes before the upgrade steps (as a pre-req), following the instructions in the external link. This is not accurate. Adjust the entry text to explain that drain is a step as part of the upgrade process and this additional information entry just mentions why it is needed. --- .../tasks/administer-cluster/kubeadm/kubeadm-upgrade.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md b/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md index 153243ffef..aa7a623c42 100644 --- a/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md +++ b/content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md @@ -37,8 +37,11 @@ The upgrade workflow at high level is the following: ### Additional information -- [Draining nodes](/docs/tasks/administer-cluster/safely-drain-node/) before kubelet MINOR version - upgrades is required. In the case of control plane nodes, they could be running CoreDNS Pods or other critical workloads. +- The instructions below outline when to drain each node during the upgrade process. +If you are performing a **minor** version upgrade for any kubelet, you **must** +first drain the node (or nodes) that you are upgrading. In the case of control plane nodes, +they could be running CoreDNS Pods or other critical workloads. For more information see +[Draining nodes](/docs/tasks/administer-cluster/safely-drain-node/). - All containers are restarted after upgrade, because the container spec hash value is changed.