Lifecycle Policy
The following defines vCluster's lifecycle policy for releases and maintenance.
vCluster follows a regular release cadence and adheres to semantic versioning. We recommend that users run the latest stable release to stay up to date with new features and security patches.
Each minor version of vCluster receives active support for 3 months from its release date. During this period, updates from the development branch can be backported upon request. After the active support phase, the version moves into maintenance support for an additional 3 months, during which backporting is restricted to security updates only.
Any versions not listed under active or maintenance support are no longer supported.
Due to vCluster's rapid development, each minor version receives active support for 3 months after its release. After this period, it transitions to maintenance support for another 3 months, during which only security fixes are applied.
Versions not listed under active or maintenance support are no longer supported.
vCluster releases​
| Release | Released | Active Support End Date | Maintenance Support End Date |
|---|---|---|---|
| v0.24 | March 18, 2025 | June 16, 2025 | September 14, 2025 |
| v0.23 | February 26, 2025 | May 25, 2025 | August 26, 2025 |
| v0.22 | December 18, 2024 | March 18, 2025 | June 18, 2025 |
| v0.21 | November 11, 2024 | February 11, 2025 | May 11, 2025 |
| v0.20 | August 14, 2024 | November 14, 2024 | February 14, 2025 |
| v0.19 | February 12, 2024 | April 1, 2025* | July 1, 2025 |
* Extended support: Due to the number of breaking changes from v0.19 to v0.20, the active support period for v0.19 has been extended. Review the migration guide to upgrade your v0.19 virtual clusters to v0.20.
- End of Support (EOS): The date when active support for a version ends. After this date, the version only receives critical security updates.
- End of Life (EOL): The date when all support, including security updates, ends for a version.
Kubernetes compatibility matrix​
The matrix below shows compatibility between host and virtual clusters running vanilla Kubernetes. It specifies which versions of vanilla Kubernetes on the host cluster support which versions on the virtual cluster.
When a new Kubernetes version is released, conformance tests are conducted on the latest vCluster version within 30 days.
Kubernetes versions that are no longer supported upstream can still be used but are not guaranteed to work.
| Host Cluster Kubernetes Version | vCluster Kubernetes Version | ||
|---|---|---|---|
| v1.32 | v1.31 | v1.30 | |
| v1.32 | ✅ | 🆗 | 🆗 |
| v1.31 | 🆗 | ✅ | 🆗 |
| v1.30 | 🆗 | 🆗 | ✅ |
- ✅ Tested and verified – Officially tested and supported.
- 🆗 Likely compatible – Expected to work, but not officially tested.