Kubernetes Version Policy

CCE provides highly scalable, high-performance, enterprise-class Kubernetes clusters. As the Kubernetes community periodically releases Kubernetes versions, CCE will release 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	Commercial Use of CCE Clusters	EOS of CCE Clusters
v1.28	In commercial use^a	August 2023	February 2024	February 2026
v1.27	In commercial use^a	April 2023	October 2023	October 2025
v1.25	In commercial use^a	August 2022	March 2023	March 2025
v1.23	In commercial use^b	December 2021	September 2022	September 2024
v1.21	In commercial use^b	April 2021	April 2022	April 2024
v1.19	EOS	August 2020	March 2021	September 2023
v1.17	End of service (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

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

CCE clusters are updated according to the versions available in the Kubernetes community. This means that a CCE cluster version is made up of both the Kubernetes community version number and the CCE patch version number. The CCE cluster version is in the format for vX.Y.Z-rN, such as v1.28.2-r0.

A Kubernetes version is in the format of X.Y, which inherits the community version policy. The major Kubernetes version is represented by X, while the minor Kubernetes version is represented by Y..
A CCE patch version is in the format of, for example, v1.28.Z-rN. New patches are released on an irregular basis for Kubernetes versions that are still in the maintenance period. If a new patch version offers new features that were not present in the previous version, the Z number will increase. If a new patch version provides bug fixes, vulnerability fixes, or scenario optimization compared to the previous version, the N number will increase.