Manual Upgrade

You can upgrade your clusters to a newer version on the CCE console.

Before the upgrade, learn about the target version to which each CCE cluster can be upgraded in what ways, and the upgrade impacts. For details, see Upgrade Overview and Before You Start.

Precautions

During the cluster upgrade, the system will automatically upgrade add-ons to a version compatible with the target cluster version. Do not uninstall or reinstall add-ons during the cluster upgrade.
Before the upgrade, ensure that all add-ons are running. If an add-on fails to be upgraded, rectify the fault and try again.
If an upgrade failure message is displayed during the cluster upgrade, rectify the fault as prompted and try again. If upgrade attempts fail again, submit a service ticket for assistance.

For more information, see Before You Start.

Procedure

The cluster upgrade goes through check, backup, configuration and upgrade, and verification.

Log in to the CCE console and click the cluster name to access the cluster console.
In the navigation pane on the left, choose Cluster Upgrade.
CCE automatically provides you with an optimal upgrade path based on the current cluster version. Select the target cluster version, check information such as version differences, and add-on versions, and click Go to Upgrade.
Perform the pre-upgrade check. Click Start Check and confirm the check. If there are abnormal or risky items in the cluster, handle the exceptions based on the check results displayed on the page and check again.
- Exceptions: View the solution displayed on the page, handle the exceptions and check again.
- Risk Items: may affect the cluster upgrade. Check the risk description and see whether you may be impacted. If no risk exists, click OK next to the risk item to manually skip this risk item and check again.
After the check is passed, click Next.

Back up the cluster. During the cluster upgrade, CCE automatically backs up etcd data. You can manually back up the control plane to speed up the rollback if the control plane fails to upgrade. If manual backup is not required, click Next.

Backup Method	Backup Object	Backup Type	Backup Time	Rollback Time	Description
etcd data backup	etcd data	Automatic backup during the upgrade	1–5 minutes	2 hours	Mandatory. The backup is automatically performed during the upgrade.
EVS snapshot backup	Control plane details, including component images, configurations, logs, and etcd data	One-click backup on web pages (manually triggered)	1–5 minutes	20 minutes	-

Configure the upgrade parameters.
- Add-on Upgrade Configuration: Add-ons that have been installed in your cluster are listed. During the cluster upgrade, CCE Autopilot automatically upgrades the selected add-ons to be compatible with the target cluster version. You can click Set to re-define the add-on parameters.
  
  If an add-on is marked with on its right side, the add-on cannot be compatible with both the source and target versions of the cluster upgrade. In this case, CCE will upgrade the add-on after the cluster upgrade. The add-on may be unavailable during the cluster upgrade.
After the configuration is complete, click Upgrade and confirm the upgrade. The cluster starts to be upgraded. You can view the process in the lower part of the page.

If an upgrade failure message is displayed during the cluster upgrade, rectify the fault as prompted and try again.
After the upgrade is complete, click Next. Verify the upgrade based on the displayed check items. After confirming that all check items are normal, click Complete and confirm that the post-upgrade check is complete. For details, see Performing Post-Upgrade Verification.

You can verify the cluster Kubernetes version on the Clusters page.