← ← Back to all products
All badges & lifecycle API →
KEDAEnd of Life (EOL) Dates & Support Status
Active
DevOps & CI/CDLatest Version: 2.21.0Latest Release: Sep 23, 2026
KEDA (Kubernetes Event-Driven Autoscaling) is an event-driven autoscaler for Kubernetes workloads.
Support summary
KEDA currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
No announced EOL date is currently listed.
Supported cycles
2
0 lts
Versions
23
Latest Version
2.21.0
Active Support
2
EOL
21
Lifecycle Timeline
Sep 28, 2023As of Sep 27, 2026
2.21Active · Date not announced
2.20Active · Date not announced
2.19EOL · Sep 23, 2026
2.18EOL · Jun 1, 2026
2.17EOL · Feb 2, 2026
2.16EOL · Oct 8, 2025
2.15EOL · Apr 7, 2025
2.14EOL · Nov 7, 2024
2.13EOL · Aug 1, 2024
2.12EOL · Apr 25, 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.21 | Sep 23, 2026 | Maintained | Date not announced | 2.21.0 | No | Active |
| 2.20 | Jun 1, 2026 | Maintained | Date not announced | 2.20.2 | No | Active |
| 2.19 | Feb 2, 2026 | Ended | Sep 23, 2026 | 2.19.0 | No | EOL |
| 2.18 | Oct 8, 2025 | Ended | Jun 1, 2026 | 2.18.3 | No | EOL |
| 2.17 | Apr 7, 2025 | Ended | Feb 2, 2026 | 2.17.3 | No | EOL |
| 2.16 | Nov 7, 2024 | Ended | Oct 8, 2025 | 2.16.1 | No | EOL |
| 2.15 | Aug 1, 2024 | Ended | Apr 7, 2025 | 2.15.1 | No | EOL |
| 2.14 | Apr 25, 2024 | Ended | Nov 7, 2024 | 2.14.1 | No | EOL |
| 2.13 | Jan 18, 2024 | Ended | Aug 1, 2024 | 2.13.1 | No | EOL |
| 2.12 | Sep 28, 2023 | Ended | Apr 25, 2024 | 2.12.1 | No | EOL |
| 2.11 | Jun 22, 2023 | Ended | Jan 18, 2024 | 2.11.2 | No | EOL |
| 2.10 | Mar 9, 2023 | Ended | Sep 28, 2023 | 2.10.1 | No | EOL |
| 2.9 | Dec 9, 2022 | Ended | Jun 22, 2023 | 2.9.3 | No | EOL |
| 2.8 | Aug 10, 2022 | Ended | Mar 9, 2023 | 2.8.2 | No | EOL |
| 2.7 | May 5, 2022 | Ended | Dec 9, 2022 | 2.7.1 | No | EOL |
| 2.6 | Jan 31, 2022 | Ended | Aug 10, 2022 | 2.6.1 | No | EOL |
| 2.5 | Nov 25, 2021 | Ended | May 5, 2022 | 2.5.0 | No | EOL |
| 2.4 | Aug 6, 2021 | Ended | Jan 31, 2022 | 2.4.0 | No | EOL |
| 2.3 | May 27, 2021 | Ended | Nov 25, 2021 | 2.3.0 | No | EOL |
| 2.2 | Mar 18, 2021 | Ended | Aug 6, 2021 | 2.2.0 | No | EOL |
| 2.1 | Jan 27, 2021 | Ended | May 27, 2021 | 2.1.0 | No | EOL |
| 2.0 | Nov 4, 2020 | Ended | Mar 18, 2021 | 2.0.0 | No | EOL |
| 1.5 | Jul 7, 2020 | Ended | Ended; date not announced | 1.5.0 | No | EOL |
Data sources
Embed this badge
Show KEDA'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/keda/)HTML
<a href="https://eol.wiki/keda/"><img src="https://eol.wiki/badge/keda.svg" alt="KEDA end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of KEDA have reached end of life?
The following KEDA versions have reached end of life and no longer receive security updates: 2.19, 2.18, 2.17, 2.16, 2.15, 2.14, 2.13, 2.12 (and 13 more). It is recommended to upgrade to a supported version.
Is it safe to continue using KEDA 2.19?
KEDA 2.19 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 KEDA?
The latest version of KEDA is 2.21.0, released in the 2.21 release cycle.
How many versions of KEDA are currently supported?
KEDA currently has 2 actively supported version(s): 2.21, 2.20.
When does KEDA 2.21 reach end of life?
KEDA 2.21 does not have a specific end-of-life date announced yet.
What should I do when KEDA reaches end of life?
When a KEDA 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.