From 076c59b6fe55a32420442e1a97c73be2526bb3fc Mon Sep 17 00:00:00 2001 From: Ron Stone Date: Wed, 25 Jan 2023 08:30:25 -0500 Subject: [PATCH] controller-0 unavailable after upgrading and unlocking (r7,r6,dsR7,dsR6) Add note before standard and duplex procedure Signed-off-by: Ron Stone Change-Id: I0798386325d010f600b2c130ba0532966d77763c --- .../kubernetes/upgrading-all-in-one-duplex-or-standard.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/source/updates/kubernetes/upgrading-all-in-one-duplex-or-standard.rst b/doc/source/updates/kubernetes/upgrading-all-in-one-duplex-or-standard.rst index 2cee02def..9c0edc81b 100644 --- a/doc/source/updates/kubernetes/upgrading-all-in-one-duplex-or-standard.rst +++ b/doc/source/updates/kubernetes/upgrading-all-in-one-duplex-or-standard.rst @@ -46,8 +46,14 @@ of |prod| software. cannot if there are locked nodes. .. note:: + The upgrade procedure includes steps to resolve system health issues. +.. note:: + + Upgrading hosts should be completed within 24 hours to avoid a kubeadm token + timeout. + .. rubric:: |proc| #. Ensure that controller-0 is the active controller.