Kubernetes Version Policy

Lifecycle of CCE Autopilot Cluster Versions

Phases of CCE Autopilot 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 Autopilot 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 Autopilot SLA is valid for such clusters.
• EOS: After the cluster version reaches its EOS, CCE Autopilot 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 Autopilot SLA is not valid for such clusters.
  

  Each CCE Autopilot cluster version has a lifecycle. For details, see Lifecycle of CCE Autopilot Cluster Versions. Running an unsupported cluster version poses significant security, reliability, and compatibility risks. Therefore, the cluster cannot be kept in a certain version indefinitely. To ensure the efficiency, availability, and security of a cluster, CCE Autopilot may automatically upgrade the cluster to the next supported, secure, and reliable version before the cluster version stops providing services.

CCE Autopilot Cluster Versions

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

• A Kubernetes version is in the format of X.Y.Z, which inherits the community version policy. The major Kubernetes version is represented by X, the minor Kubernetes version is represented by Y, and the Kubernetes patch version is represented by Z. For details, see the Kubernetes version policies. For details about the Kubernetes versions supported by CCE Autopilot, see Kubernetes Version Release Notes.
• A CCE Autopilot patch version is in the format of, for example, v1.30.4-rN. New patches are released on an irregular basis for Kubernetes versions that are still in the maintenance period. If a new patch version provides new features, bug fixes, vulnerability fixes, or scenario optimizations compared with the previous version, the N version number increases. For details about the patch versions, see CCE Autopilot Cluster Patch Release History.

Cluster Upgrade

Periodically upgrade CCE Autopilot clusters for better user experience. Using an EOS version, you cannot obtain technical support and CCE Autopilot SLA assurance. Upgrade CCE Autopilot 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. For details, see Upgrade Overview.