docs/doc/source/updates/kubernetes/configuring-kubernetes-update-orchestration.rst

Create Kubernetes Version Upgrade Cloud Orchestration Strategy

You can configure Kubernetes Upgrade Orchestration Strategy using the sw-manager CLI.

Note

You require administrator privileges to use sw-manager. You must log in to the active controller as user sysadmin and source the script by using the command, source /etc/platform/openrc to obtain administrator privileges. Do not use sudo.

Note

Management-affecting alarms cannot be ignored using relaxed alarm rules during an orchestrated Kubernetes version upgrade operation. For a list of management-affecting alarms, see : Alarm Messages <100-series-alarm-messages-starlingx>. To display management-affecting active alarms, use the following command:

~(keystone_admin)$ fm alarm-list --mgmt_affecting

During an orchestrated Kubernetes version upgrade operation, the following alarms are ignored even when the default strict restrictions are selected:

• 100.103: Memory threshold exceeded.
• 100.119: alarm for SyncE
• 200.001: Locked host.
• 280.001: Subcloud resource off-line.
• 280.002: Subcloud resource out-of-sync.
• 700.004: stopped.
• 750.006: Configuration change requires reapply of cert-manager.
• 900.007: Kube upgrade in progress.
• 900.022: Clean up deployment data.
• 900.023: Software release deploy operation in progress
• 900.401: kube-upgrade-auto-apply-inprogress.
• 900.701: Node tainted

You can use help for the overall commands and also for each sub-command. For example:

~(keystone_admin)$ sw-manager kube-upgrade-strategy –help
usage: sw-manager kube-upgrade-strategy [-h]  ...
optional arguments:
  -h, --help  show this help message and exit
Kubernetes Update Commands:
    create    Create a strategy
    delete    Delete a strategy
    apply     Apply a strategy
    abort     Abort a strategy
    show      Show a strategy

• Hosts that need to be upgraded must be in the unlocked-enabled state.
• If you are using NetApp Trident, ensure that your NetApp backend version is compatible with Trident 25.02.1 before upgrading Kubernetes to version and after updating to version . For more information, see Upgrade the NetApp Trident Software <upgrade-the-netapp-trident-software-c5ec64d213d3>.

Note

The sysadmin and admin passwords must be set to the same value prior to starting an upgrade from Release to Release .

partner

For more details, see the section Kubernetes Upgrade using Cloud Orchestration for AIO-SX and Multi-Nodes <configuring-kubernetes-multi-version-upgrade-orchestration-aio-b0b59a346466> .