Add patch-strategy removal to orchestration upgrade requirements
Change-Id: I851c58ca9e9dd9ec3c7653a1c5646e851df74aee Signed-off-by: Keane Lim <keane.lim@windriver.com>
This commit is contained in:
@@ -66,8 +66,9 @@ conditions:
|
|||||||
- An upgrade has been started, and controller-1 has been upgraded and is
|
- An upgrade has been started, and controller-1 has been upgraded and is
|
||||||
active.
|
active.
|
||||||
|
|
||||||
- No update orchestration strategy exists. An upgrade cannot be orchestrated
|
- No orchestration strategy exists. Patch, upgrade, firmware, kubernetes,
|
||||||
while update orchestration is in progress.
|
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
|
- Sufficient free capacity or unused worker resources must be available
|
||||||
across the cluster. A rough calculation is: Required spare capacity \( %\)
|
across the cluster. A rough calculation is: Required spare capacity \( %\)
|
||||||
|
|||||||
Reference in New Issue
Block a user