From 867d2ca00b8ab7f6ddc8612c554368b29ddfd1bc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Miquel=20Sabat=C3=A9=20Sol=C3=A0?= Date: Tue, 11 Aug 2020 15:15:16 +0200 Subject: [PATCH] Reflect cordon & drain operations on update (#959) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit When updating a node, skuba will cordon/drain the node before starting the operation, and it will uncordon/undrain it whenever the update has been applied successfully. This might not be expected by the user, so we better document it. See SUSE/doc-caasp#774 See SUSE/avant-garde#1842 See SUSE/skuba#1298 Signed-off-by: Miquel Sabaté Solà --- adoc/admin-updates.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/adoc/admin-updates.adoc b/adoc/admin-updates.adoc index 2387f9b58..1e8924a56 100644 --- a/adoc/admin-updates.adoc +++ b/adoc/admin-updates.adoc @@ -259,6 +259,7 @@ The upgrade via `skuba node upgrade apply` will: * upgrade the containerized control plane. * upgrade the rest of the {kube} system stack (`kubelet`, `cri-o`). +* temporarily drain/cordon the node before starting the whole process, and then undrain/uncordon the node after the upgrade has been successfully applied. * restart services. ====