starlingx/docs
Code Issues Proposed changes
docs/doc/source/updates/kubernetes/about-kubernetes-orchestrated-upgrades.rst
Ron Stone f125a8b892 Remove spurious escapes (r8,dsR8) 
This change addresses a long-standing issue in rST documentation imported from XML.
That import process added backslash escapes in front of various characters. The three
most common being '(', ')', and '_'.
These instances are removed.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Id43a9337ffcd505ccbdf072d7b29afdb5d2c997e
2023-03-01 11:19:04 +00:00

2.5 KiB
Raw Blame History

About Kubernetes Version Upgrade Cloud Orchestration

Kubernetes version upgrade cloud orchestration allows the Kubernetes version on all hosts of an entire cloud to be updated with a single operation.

You can configure and run Kubernetes version upgrade cloud orchestration using the CLI, or the stx-nfv VIM REST API.

Kubernetes Version Upgrade Cloud Orchestration Requirements

Kubernetes version upgrade orchestration can only be done on a system that meets the following conditions:

  • The system is clear of alarms (with the exception of alarms for locked hosts, stopped instances, and Kubernetes version upgrade cloud orchestration in progress).

    Note

    When configuring Kubernetes version upgrade cloud orchestration, you have the option to ignore alarms that are not management-affecting severity. For more information, see Kubernetes Version Upgrade Cloud Orchestration <configuring-kubernetes-update-orchestration>.

  • There are unlocked-enabled worker function hosts in the system that requires Kubernetes Version Upgrade Cloud Orchestration. The Kubernetes 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 -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 and have upgraded from the previous version, ensure that your NetApp backend version is compatible with Trident 22.01 and follow the steps in Upgrade the NetApp Trident Software <upgrade-the-netapp-trident-software-c5ec64d213d3> to upgrade the Trident drivers to 22.01 before upgrading Kubernetes to version .

    Note

    Administrative controller swact operations should be avoided during Kubernetes version upgrade orchestration.