Upgrade Workload Clusters
Use this page after the global cluster is upgraded; in a DR environment, after both global clusters are upgraded; when the standby is upgraded after the workload clusters, use this page once the primary is upgraded, then return to Upgrade the Workload Clusters. Each workload cluster moves to the ACP version (Distribution Version) that global runs now. Unless a step says otherwise, run the commands from the execution host, logged in with ac login, on the global cluster, which is the primary global cluster in a DR environment. Commands for a workload cluster itself run after ac config use-cluster <cluster-name>; switch back with ac config use-cluster global.
Do not start another global upgrade while a workload cluster upgrade is running; the platform does not block it. The global upgrade pages check this before the upgrade. See Upgrade Order and Compatibility.
Before You Upgrade the Clusters
Complete these steps for each cluster that you plan to upgrade, before you request its upgrade.
Confirm the Standby global Cluster Is Upgraded
Applies to: DR environments. Skip it while synchronization is paused. Run Preflight Checks for the Cluster checks the primary.
On the standby, where ac whoami --show-server prints the standby VIP:
Continue when Current shows the target ACP version and the Ready condition is True; otherwise, finish the upgrade of the standby first.
Make Operator Packages Available
Applies to: a cluster that did not receive the target packages of its installed Operators with the Aligned lifecycle during preparation, for example a cluster added later. Skip it for other clusters.
From the execution host, push the target package of each Aligned Operator installed on the cluster. Set --dest-repo to the registry that the cluster uses, with its credentials; see Addresses and Credentials.
Check the etcd Backup
Applies to: workload clusters created by ACP. Skip it for imported and registered clusters.
On the workload cluster, list its backup records:
Run Preflight Checks for the Cluster
Run this block on the global cluster, the primary in a DR environment, in the installer/ directory of the extracted target Core Package; ac whoami --show-server prints an address that ends with /kubernetes/global/:
On the workload cluster, list the patches, review each of them, then exempt it with the target version as the value; do not use *:
Check the Cluster by Type
Applies to: every cluster that you upgrade, except imported clusters. Use the Non-Alauda OS tab for a cluster that ACP created on nodes without Alauda OS, and the tab of the infrastructure provider for an Alauda OS cluster.
Run each block on the execution host unless it says that it runs on a node or a host. Each table has a Continue row for each part of the output: continue when every part matches its Continue row; otherwise, take the action of each row that matches.
On each node of the cluster:
Continue when the kernel is 5.8 or later and within Supported OS and Kernel Versions, and the second command prints cgroup2fs; otherwise, update the OS of the node before you upgrade the cluster, and if you cannot, contact technical support. The update restarts the node.
Check DR Synchronization
Applies to: DR environments. Skip it on a platform without a standby global cluster, and while synchronization is paused.
Run the check on a control plane node of the standby global cluster, then return to the execution host:
Upgrade a Workload Cluster
Request the Upgrade
An upgrade cannot be rolled back. On Huawei DCS, Huawei Cloud Stack, and VMware vSphere, the request also replaces every node with a new VM, one at a time; on Bare Metal, it reinstalls every host, one at a time. This happens on every minor upgrade, and on a patch upgrade when the target changes the Kubernetes build or the Alauda OS image.
Select the global cluster, list the available updates of the workload cluster, then request the version it lists as <target-version>, for example 4.5.0. Each cluster has its own request; repeat it for each cluster that you upgrade. The platform upgrades a limited number of clusters at the same time, and the rest wait.
Monitor the Upgrade
Run the commands again until Current shows the target version and the Ready condition is True; add --verbose to see every check and stage. If Upgrade shows Blocked or Retrying, see Inspect Upgrade State. On Alauda OS, if the upgrade stays InProgress in the Kubernetes stage, read the Stalled condition of the InfraClusterVersion as described there. Fix the reported cause and the upgrade continues; if it cannot be fixed, contact technical support.
On Alauda OS, CURRENT of the InfraClusterVersion advances through each intermediate Kubernetes version; also wait until CURRENT equals DESIRED and PHASE is Succeeded. Until then, do not edit the cluster's KubeadmControlPlane, MachineDeployment resources, or their templates.
Upgrade the Agnostic Extensions
The upgrade request does not upgrade Extensions (Operators and Cluster Plugins) with the Agnostic lifecycle. Upgrade each Agnostic Extension separately by following its own documentation; while synchronization is paused, upgrade them after it is resumed. For example:
Validate the Cluster
Complete Upgrade Validation for each workload cluster that you upgraded to finish its upgrade.