← ← Back to all products
All badges & lifecycle API →
KumaEnd of Life (EOL) Dates & Support Status
Active
DevOps & CI/CDLatest Version: 2.14.5Latest Release: Sep 18, 2026
Kuma is a universal service mesh for both Kubernetes and VM-based workloads.
Support summary
Kuma 2.7 reaches EOL in 22 days. Start upgrade planning and compatibility testing now.
What do EOL and support statuses mean?Next EOL
Oct 19, 2026
Kuma 2.7 · 22 days left
Supported cycles
5
1 lts
Versions
22
Latest Version
2.14.5
Active Support
5
EOL
17
Lifecycle Timeline
Nov 15, 2023As of Sep 27, 2026
2.14Active · Jun 12, 2027
2.13Active · Dec 22, 2027
2.12EOL · Sep 9, 2026
2.11Active · Dec 10, 2026
2.10EOL · Mar 20, 2026
2.9Active · Oct 22, 2026
2.8EOL · Jun 24, 2025
2.7Active · Oct 19, 2026
2.6EOL · Feb 1, 2025
2.5EOL · Nov 15, 2024
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 2.14 | Jun 12, 2026 | Maintained | Jun 12, 2027 | 2.14.5 | No | Active |
| 2.13 | Dec 22, 2025 | Maintained | Dec 22, 2027 | 2.13.11 | No | Active |
| 2.12 | Sep 9, 2025 | Ended | Sep 9, 2026 | 2.12.15 | No | EOL |
| 2.11 | Jun 10, 2025 | Maintained | Dec 10, 2026 | 2.11.19 | No | Active |
| 2.10 | Mar 20, 2025 | Ended | Mar 20, 2026 | 2.10.11 | No | EOL |
| 2.9 | Oct 22, 2024 | Maintained | Oct 22, 2026 | 2.9.20 | No | Active |
| 2.8 | Jun 24, 2024 | Ended | Jun 24, 2025 | 2.8.8 | No | EOL |
| 2.7 | Apr 19, 2024 | Maintained | Oct 19, 2026 | 2.7.30 | Yes | Active |
| 2.6 | Feb 1, 2024 | Ended | Feb 1, 2025 | 2.6.15 | No | EOL |
| 2.5 | Nov 15, 2023 | Ended | Nov 15, 2024 | 2.5.11 | No | EOL |
| 2.4 | Aug 29, 2023 | Ended | Aug 29, 2024 | 2.4.10 | No | EOL |
| 2.3 | Jun 23, 2023 | Ended | Jun 23, 2024 | 2.3.7 | No | EOL |
| 2.2 | Apr 14, 2023 | Ended | Apr 14, 2024 | 2.2.9 | No | EOL |
| 2.1 | Jan 30, 2023 | Ended | Feb 1, 2024 | 2.1.7 | No | EOL |
| 2.0 | Nov 4, 2022 | Ended | Nov 4, 2023 | 2.0.8 | No | EOL |
| 1.8 | Aug 22, 2022 | Ended | Aug 24, 2023 | 1.8.8 | No | EOL |
| 1.7 | Jun 13, 2022 | Ended | Jun 16, 2023 | 1.7.6 | No | EOL |
| 1.6 | Apr 11, 2022 | Ended | Apr 12, 2023 | 1.6.5 | No | EOL |
| 1.5 | Feb 24, 2022 | Ended | Feb 24, 2023 | 1.5.5 | No | EOL |
| 1.4 | Nov 19, 2021 | Ended | Nov 22, 2022 | 1.4.1 | No | EOL |
| 1.3 | Aug 24, 2021 | Ended | Aug 26, 2022 | 1.3.1 | No | EOL |
| 1.2 | Jun 17, 2021 | Ended | Jun 17, 2022 | 1.2.3 | No | EOL |
Data sources
Sources
Embed this badge
Show Kuma's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/kuma/)HTML
<a href="https://eol.wiki/kuma/"><img src="https://eol.wiki/badge/kuma.svg" alt="Kuma end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Kuma have reached end of life?
The following Kuma versions have reached end of life and no longer receive security updates: 2.12, 2.10, 2.8, 2.6, 2.5, 2.4, 2.3, 2.2 (and 9 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Kuma 2.12?
Kuma 2.12 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 Kuma?
The latest version of Kuma is 2.14.5, released in the 2.14 release cycle.
How many versions of Kuma are currently supported?
Kuma currently has 5 actively supported version(s): 2.14, 2.13, 2.11, 2.9, 2.7.
When does Kuma 2.14 reach end of life?
Kuma 2.14 is scheduled to reach end of life on Jun 12, 2027.
What should I do when Kuma reaches end of life?
When a Kuma 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.