Upgrade Validation
Validate each upgraded cluster to finish its upgrade. In a DR environment, validate the standby and the primary global cluster separately, before you upgrade any workload cluster; when the standby is upgraded after the workload clusters, validate the primary before the workload clusters and the standby after its upgrade. The upgrade of a cluster is finished when every check on this page passes.
Run the commands on this page from the execution host, on the global cluster, which is the primary in a DR environment, for the global cluster and for every workload cluster; ac whoami --show-server prints an address that ends with /kubernetes/global/:
To validate the standby global cluster in a DR environment, run export KUBECONFIG=<standby-kubeconfig> instead, confirm that ac whoami --show-server prints the standby VIP, keep it for every block on this page, skip the ac config use-cluster lines, and run unset KUBECONFIG when you finish.
TOC
Check the ACP VersionCheck Kubernetes, Nodes, and ExtensionsAdditional Checks for Alauda OS ClustersCheck the Kube-OVN and CoreDNS TakeoverCheck the Provider ResourcesCheck the Web UINext StepAfter All Clusters Are UpgradedCheck the ACP Version
Replace <cluster-name> with global or the workload cluster name:
Continue when Upgrade is Completed, Current shows the target ACP version (Distribution Version), the Ready condition is True, Stalled is not True, and the first history entry shows the target version with the state Completed; otherwise, follow Inspect Upgrade State.
Check Kubernetes, Nodes, and Extensions
On the global cluster, read the Core and the installed Extensions of the cluster:
Then read Kubernetes, the nodes, and the Pods on the upgraded cluster itself. For a workload cluster, the first line switches to it and the last line switches back to global; for a global cluster, skip both lines:
Additional Checks for Alauda OS Clusters
Applies to: Alauda OS clusters. Skip it for non-Alauda OS clusters.
Check the Kube-OVN and CoreDNS Takeover
On the global cluster, use the kind that matches the provider of the cluster, dcscluster, baremetalcluster, hcscluster, or vspherecluster:
Check the Provider Resources
On the global cluster, run the checks for the provider of the cluster:
Check the Web UI
Open the platform Web UI. Continue when login, cluster pages, and Marketplace pages load, and, for each Extension with the Agnostic lifecycle that you upgraded, its pages open; otherwise, contact technical support.
Next Step
After you validate the global clusters, continue with Upgrade Workload Clusters. After you validate a workload cluster, return to that page for the next cluster. After the last cluster, continue with After All Clusters Are Upgraded.
After All Clusters Are Upgraded
When global and every workload cluster run the target ACP version:
- If the source ACP version was earlier than 4.3 and the PKCE hardening is not done yet, follow Disabling the PKCE Plain Method.
- Delete a VM template, cloud image, or Bare Metal OS image of an earlier version only after the last cluster that uses it is upgraded.