Cluster Upgrade¶
The Kubernetes Community packages a small version every quarter, and the maintenance cycle of each version is only about 9 months. Some major bugs or security holes will not be updated after the version stops maintenance. Manually upgrading cluster operations is cumbersome and places a huge workload on administrators.
In DCE, you can upgrade the Kubernetes cluster with one click through the web UI interface.
Danger
After the version is upgraded, it will not be possible to roll back to the previous version, please proceed with caution.
Note
- Kubernetes versions are denoted as x.y.z , where x is the major version, y is the minor version, and z is the patch version.
- Cluster upgrades across minor versions are not allowed, e.g. a direct upgrade from 1.23 to 1.25 is not possible.
- **Access clusters do not support version upgrades. If there is no "cluster upgrade" in the left navigation bar, please check whether the cluster is an access cluster. **
- The global service cluster can only be upgraded through the terminal.
- When upgrading a working cluster, the Management Cluster of the working cluster should have been connected to the container management module and be running normally.
-
Click the name of the target cluster in the cluster list.
-
Then click Cluster Operation and Maintenance -> Cluster Upgrade in the left navigation bar, and click Version Upgrade in the upper right corner of the page.
-
Select the version that can be upgraded, and enter the cluster name to confirm.
-
After clicking OK , you can see the upgrade progress of the cluster.
-
The cluster upgrade is expected to take 30 minutes. You can click the Real-time Log button to view the detailed log of the cluster upgrade.