Updates to clean up step numbering for Kubernetes Versions (dsr8MR2, dsr8MR3)

Story: 2011124
Task: 50150

Change-Id: If46d965efe9504b1318f611e5d3a191f8131cd7f
Signed-off-by: Juanita Balaraj <juanita.balaraj@windriver.com>
This commit is contained in:
Juanita Balaraj 2024-07-17 20:42:19 +00:00 committed by Juanita-Balaraj
parent 56c38b03bb
commit afc8ce7dd6

View File

@ -125,7 +125,7 @@ system. This feature is not supported in the system which is not |AIO-SX|.
.. code-block:: none
~(keystone_admin)]$ system kube-upgrade-start 1.24.4
~(keystone_admin)]$ system kube-upgrade-start v1.24.4
+--------------+--------------------------------------+
| Property | Value |
+--------------+--------------------------------------+
@ -318,13 +318,13 @@ system. This feature is not supported in the system which is not |AIO-SX|.
The status **upgraded-kubelet** will be entered when the kubelet upgrade
has completed.
Repeat steps 9 and 10 to reach the target Kubernetes version. For example, in
this case, we need to repeat steps 9 and 10 twice for the remaining
Repeat steps 8 and 9 to reach the target Kubernetes version. For example, in
this case, we need to repeat steps 8 and 9 twice for the remaining
versions v1.23.1 and v1.24.4.
#. |optional| Run the ``uncordon`` subcommand.
Skip this step if you did not perform step 8.
Skip this step if you did not perform step 7.
The :command:`kube-host-uncordon` command will allow the regular pods on the
host again.