ACK Lingjun clusters support Kubernetes versions aligned with the open source community. This topic covers the release history, version format, upgrade rules, and end-of-life (EOL) policy for ACK Lingjun clusters.
Release history
| Version | Status | Release date | End of life date |
|---|---|---|---|
| 1.31 | Released | Jan 2025 | Subject to the actual situation of ACK Lingjun clusters |
| 1.30 | Released | Jan 2025 | Subject to the actual situation of ACK Lingjun clusters |
| 1.28 | Released | Dec 2023 | Subject to the actual situation of ACK Lingjun clusters |
| 1.22 | Outdated | Nov 2023 | Subject to the actual situation of ACK Lingjun clusters |
| 1.20 | Outdated | Apr 2023 | Nov 2023 |
Version format
ACK Lingjun clusters use the x.y.z-aliyun.n semantic versioning format, where x.y.z maps to the open source Kubernetes version:
x: major version — API compatibility changesy: minor version — feature enhancementsz: patch version — bug fixesn: Alibaba Cloud patch version
For example, version 1.31.1-aliyun.1 is based on open source Kubernetes 1.31.1. For details on the Kubernetes versioning scheme, see Kubernetes Release Versioning.
Minor version release cadence
Starting January 2025 (Kubernetes 1.31), ACK Lingjun clusters expanded support from even-numbered minor versions only (such as 1.28 and 1.30) to all minor versions. Actual release dates follow the ACK Lingjun cluster release schedule. After each new version release, ACK Lingjun clusters periodically publish patch versions for feature updates and vulnerability fixes.
Version support policy
Cluster creation
ACK Lingjun clusters support creating clusters on the three most recent minor versions (N, N-1, and N-2). Currently supported versions are 1.31, 1.30, and 1.28.
The following restrictions apply:
When a new minor version (N) becomes available, the oldest supported minor version (N-3) is no longer available for new cluster creation. For example, when Kubernetes 1.31 becomes available, versions before 1.28 can no longer be used to create clusters.
When a new patch version is released, earlier patch versions within the same minor version are disabled. For example, when version 1.30.7 is released, clusters on version 1.30.1 can no longer be created.
Cluster upgrade
Upgrades follow a sequential minor version path — cross-version upgrades and rollbacks are not supported.
Supported upgrade paths:
| From | To | Supported |
|---|---|---|
| 1.28.x | 1.30.x | Yes |
| 1.30.x | 1.31.x | Yes |
| 1.28.x | 1.31.x | No — upgrade to 1.30 first |
For example, to upgrade a cluster from 1.28 to 1.31, first upgrade from 1.28 to 1.30, then from 1.30 to 1.31.
For patch versions, clusters can only be upgraded to the latest patch version within the same minor version.
Technical support
For maintained versions, ACK Lingjun clusters provide comprehensive technical support, including Q&A assistance, real-time guidance, fault diagnosis, and issue resolution. Support is gradually discontinued for versions that are no longer maintained.
EOL Kubernetes versions
End-of-life (EOL) versions may contain security vulnerabilities and stability risks. Upgrade clusters running EOL versions as soon as possible.
For EOL versions, ACK Lingjun clusters cease security patch delivery and bug resolution, and technical support transitions to a best-effort basis.