6db00e3642
Story: 2011415 Update 12: Addressed Patchset 14 comments. Update 11: Addresses Patchset 13 comment. Update 10: Addressed Patchset 12 comments. Update 9: Addressed some of the Patchset 11 comments. Update 8: Please review the latest updates based on discussion and email that was sent last week. Update7: Addressed Patchset 9 comments. Update6: Addressed Patchset 8 comments. Update5: Addressed comments received on Patchset 7 onwards. Update4: Addressed all comments received so far. Update3: Addressed comments from previous patchset and also added new steps for multi-version upgrades. Update2: Addressed comments given in two files. Need to clarify comments for the third file. Update 1: Updated version and also added details for semantic version skew policy checking Change-Id: I1f689931572bf1f252b4e005ec226f17a761b867 Signed-off-by: Petsy Mathew <petsy.mathew@windriver.com>
2.9 KiB
About Kubernetes Upgrade Cloud Orchestration
Kubernetes 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.
Note
The ability to abort and rollback during a Kubernetes multi-version upgrade is only supported for configuration. For multi-node clusters, while multi-version Kubernetes upgrades are now supported (as of ), abort and rollback are not available.
Kubernetes Upgrade Cloud Orchestration Requirements
Kubernetes 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 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 -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 25.02.1 and follow the steps in
Upgrade the NetApp Trident Software <upgrade-the-netapp-trident-software-c5ec64d213d3>to upgrade the Trident drivers to 25.02.1 before upgrading Kubernetes to version .Note
Avoid administrative controller
swactoperations during Kubernetes version upgrade orchestration.