From bbe8e4fc8db4e8610d5f1f8a4f08baf552cd758b Mon Sep 17 00:00:00 2001 From: Keane Lim Date: Tue, 28 Sep 2021 12:17:18 -0400 Subject: [PATCH] Add patch-strategy removal to orchestration upgrade requirements Change-Id: I851c58ca9e9dd9ec3c7653a1c5646e851df74aee Signed-off-by: Keane Lim --- .../updates/kubernetes/orchestration-upgrade-overview.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/source/updates/kubernetes/orchestration-upgrade-overview.rst b/doc/source/updates/kubernetes/orchestration-upgrade-overview.rst index 77e01e62f..baf8d198b 100644 --- a/doc/source/updates/kubernetes/orchestration-upgrade-overview.rst +++ b/doc/source/updates/kubernetes/orchestration-upgrade-overview.rst @@ -66,8 +66,9 @@ conditions: - An upgrade has been started, and controller-1 has been upgraded and is active. -- No update orchestration strategy exists. An upgrade cannot be orchestrated - while update orchestration is in progress. +- No orchestration strategy exists. Patch, upgrade, firmware, kubernetes, + and kube rootca are all types of orchestration. An upgrade cannot be + orchestrated while another orchestration is in progress. - Sufficient free capacity or unused worker resources must be available across the cluster. A rough calculation is: Required spare capacity \( %\)