From 5d4e9270907330cb4f33411d1a953b769d7b699e Mon Sep 17 00:00:00 2001 From: Elaine Fonaro Date: Tue, 13 Sep 2022 10:25:59 -0300 Subject: [PATCH] Update system limits based on 2+2+50 testing (r7) - Back to the original note. - Rewrote the note. - Added a note regarding the parameter max-parallel-worker-hosts. Signed-off-by: Elaine Fonaro Change-Id: Iedacf6b3397cb5daf84096bcbea70f92ab926b53 --- .../updates/kubernetes/performing-an-orchestrated-upgrade.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/source/updates/kubernetes/performing-an-orchestrated-upgrade.rst b/doc/source/updates/kubernetes/performing-an-orchestrated-upgrade.rst index 7c8db7413..5896e548c 100644 --- a/doc/source/updates/kubernetes/performing-an-orchestrated-upgrade.rst +++ b/doc/source/updates/kubernetes/performing-an-orchestrated-upgrade.rst @@ -93,6 +93,10 @@ described below to upgrade the remaining nodes of the |prod| system. Specify the maximum worker hosts to upgrade in parallel \(minimum: 2, maximum: 10\). + .. note:: + For a maximum worker hosts condition in a Standard configuration + (50), the value shall be at the maximum 2, which represents the + minimum value. **alarm-restrictions** This option lets you specify how upgrade orchestration behaves when