Kubernetes Version Policy

CCE provides highly scalable, high-performance, enterprise-class Kubernetes clusters. As the Kubernetes community periodically releases Kubernetes versions, CCE will release cluster Open Beta Test (OBT) and commercially used versions accordingly. This section describes the Kubernetes version policy of CCE clusters.

Lifecycle of CCE Cluster Versions

Kubernetes Version	Status	Community Release In	OBT of CCE Cluster Version In	Commercial Use of CCE Cluster Version In	EOS of CCE Cluster Version In
v1.25	In commercial use^a	August 2022	November 2022	March 2023	March 2025
v1.23	In commercial use^a	December 2021	April 2022	September 2022	September 2024
v1.21	In commercial use^b	April 2021	December 2021	April 2022	April 2024
v1.19	In commercial use^b	August 2020	December 2020	March 2021	September 2023
v1.17	EOS	December 2019	/	July 2020	January 2023
v1.15	EOS	June 2019	/	December 2019	September 2022
v1.13	EOS	December 2018	/	June 2019	March 2022
v1.11	EOS	August 2018	/	October 2018	March 2021
v1.9	EOS	December 2017	/	March 2018	December 2020

The CCE console supports clusters of the latest two commercially used versions:

a: Clusters created using the console or APIs
b: Clusters created only using APIs

Phases of CCE Cluster Versions

OBT: You can experience the latest features of this cluster version. However, the stability of clusters of this version has not been completely verified, and the Service Level Agreement (SLA) of CCE is not valid for such clusters.
In commercial use: The cluster version has been fully verified and is stable and reliable. You can use clusters of this version in the production environment, and the CCE SLA is valid for such clusters.
EOS: After the cluster version EOS, CCE does not support the creation of new clusters or provide technical support including new feature updates, vulnerability or issue fixes, new patches, work order guidance, and online checks for the EOS cluster version. The CCE SLA is not valid for such clusters.

CCE Cluster Versions

Cluster version: The format is x.y, where x indicates the major Kubernetes version and y indicates the minor Kubernetes version. For details, see the Kubernetes community documentation.
Patch version: The format is x.y.z-r(n), where x.y indicates the CCE cluster version, z indicates the minor CCE version, and -r(n) indicates the patch version.

Figure 1 Cluster version

CCE Cluster Upgrade Policy

Periodically upgrade CCE clusters for better user experience. Using an EOS version, you cannot obtain technical support and CCE SLA assurance. Upgrade CCE clusters in a timely manner.

On the CCE console, you can easily upgrade clusters in a visualized manner, improving the stability and reliability of clusters.

Cluster upgrade

CCE clusters support cross-version upgrade. For details, see Table 1.