From 7208de42336638cba46c21c61a01bef8cc77ee28 Mon Sep 17 00:00:00 2001 From: Ngairangbam Mili Date: Wed, 12 Mar 2025 05:49:30 +0000 Subject: [PATCH] Kubernetes version upgrade is not a reboot required operation for AIO-SX only (r10, dsr10, dsr10 minor) Change-Id: Id95f22239605170965106d9b3c96a7667ee25ccd Signed-off-by: Ngairangbam Mili --- .../about-kubernetes-orchestrated-upgrades.rst | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/doc/source/updates/kubernetes/about-kubernetes-orchestrated-upgrades.rst b/doc/source/updates/kubernetes/about-kubernetes-orchestrated-upgrades.rst index a2077eed9..cd5befc73 100644 --- a/doc/source/updates/kubernetes/about-kubernetes-orchestrated-upgrades.rst +++ b/doc/source/updates/kubernetes/about-kubernetes-orchestrated-upgrades.rst @@ -40,11 +40,13 @@ meets the following conditions: Upgrade Orchestration Strategy* creation step will fail if there are no qualified hosts detected. - A Kubernetes version upgrade is a reboot required operation. Therefore, in - systems that have the |prefix|-openstack application applied with running - instances, if the migrate option is selected there must be spare - openstack-compute (worker) capacity to move instances off the - openstack-compute (worker) host\(s) being upgraded. + A Kubernetes version upgrade requires replacing kubelet on each node, which + requires the applications on each node to be disrupted. In the multi-node + clusters, a Kubernetes version upgrade also requires a host lock/unlock. + Therefore, in the multi-node systems that have the |prefix|-openstack application + applied with running instances, if the migrate option is selected, there + must be spare openstack-compute (worker) capacity to move instances off the + openstack-compute (worker) host(s) being upgraded. - If you are using NetApp Trident in |prod| |prod-ver| and have upgraded from the |prod| previous version, ensure that your NetApp backend version is