← ← Back to all products
KubeSphere
Active
Cloud & Platforms Latest Version: 4.2.1 Latest Release: Jan 12, 2026
KubeSphere is an open-source distributed operating system that provides a multi-cluster management plane on Kubernetes.
Versions
6
Latest Version
4.2.1
Active Support
2
EOL
4
Lifecycle Timeline
Today ↓
4.2
4.2
4.1
4.1
4.0
4.0
3.5
3.5
3.4
3.4
3.3
3.3
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 4.2 | Jul 14, 2025 | Jul 14, 2028 | Mar 14, 2030 | 4.2.1 | No | Active |
| 4.1 | Apr 16, 2024 | Apr 16, 2027 | Dec 16, 2028 | 4.1.3 | No | Active |
| 4.0 | Aug 16, 2023 | No | Jun 28, 2024 | 4.0.0 | No | EOL |
| 3.5 | Oct 13, 2023 | Jul 13, 2025 | Mar 13, 2026 | 3.5.0 | No | EOL |
| 3.4 | Apr 25, 2023 | May 25, 2025 | Dec 25, 2025 | 3.4.1 | No | EOL |
| 3.3 | Jun 24, 2022 | Mar 31, 2025 | Oct 31, 2025 | 3.3.2 | No | EOL |
Frequently Asked Questions
Which versions of KubeSphere have reached end of life?
The following KubeSphere versions have reached end of life and no longer receive security updates: 4.0, 3.5, 3.4, 3.3. It is recommended to upgrade to a supported version.
Is it safe to continue using KubeSphere 4.0?
KubeSphere 4.0 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of KubeSphere?
The latest version of KubeSphere is 4.2.1, released in the 4.2 release cycle.
How many versions of KubeSphere are currently supported?
KubeSphere currently has 2 actively supported version(s): 4.2, 4.1.
When does KubeSphere 4.2 reach end of life?
KubeSphere 4.2 is scheduled to reach end of life on Mar 14, 2030.
What should I do when KubeSphere reaches end of life?
When a KubeSphere version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.