Skip to main content
Version: main 🚧

Lifecycle policy

The following defines the platform's lifecycle policy for releases and maintenance.

The platform aims to release on a regular cadence and follow semantic versioning. We encourage users to run the latest stable release to stay up to date on features and security patches.

Due to the rapid development of the platform, each minor version receives active support for 6 months after its release. Active support ends on the End of Support (EOS) end date. After the EOS end date, the version enters End of Life (EOL), during which only critical security updates are backported. During active support, updates from the active development branch can be backported upon request.

Any previous versions which are not on the following list, are no longer in any support window.

Platform supported versions​

ReleaseReleasedEnd of Support (EOS) End DateEnd of Life (EOL) End Date
v4.92026 Apr 292026 Oct 292027 Jan 29
v4.82026 Mar 162026 Sep 162026 Dec 16
v4.72026 Feb 182026 Aug 182026 Nov 18
v4.62026 Jan 292026 Jul 292026 Oct 29
v4.52025 Oct 292026 Apr 292026 Jul 29
v4.42025 Sep 092026 Mar 092026 Jun 09
Versions below are no longer supported
v4.32025 Jun 032025 Dec 032026 Mar 06
v4.22024 Dec 172025 Sep 172025 Dec 17
v4.12024 Nov 122025 Feb 122025 May 12
v4.02024 Oct 152025 Jan 152025 Apr 15
v3.42024 Feb 292025 Apr 01*2025 Jul 01

* Due to the number of breaking changes from vCluster v0.19 to v0.20 and vCluster Platform v3.4 to v4.0, v3.4 has an extended EOS end date. Review the migration guide to upgrade your platform from v3.4 to v4.0.

Support terminology
  • End of Support (EOS): The period when active support for a version has ended and only critical security updates are provided. This period begins on the EOS date and lasts 3 months.

  • End of Life (EOL): The period when all support, including security updates, has ended for a version. This period begins on the EOL date and continues indefinitely.

Feature Versioning​

While most features we release are fully supported, some are introduced at an earlier stage of development. These stages generally align with Kubernetes conventions, with the exception of experimental features which may be removed at any time.

  • Alpha: Newly introduced features which may include breaking changes in future releases.

  • Beta: Features that are more stable and considered safe, but not recommended for business critical applications.