KEDA End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all KEDA versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.5 | 1.5.0 | Jul 7, 2020 | No EOL date | Supported | Active |
| 2.0 | 2.0.0 | Nov 4, 2020 | Mar 18, 2021 | 1923 days past EOL | EOL |
| 2.1 | 2.1.0 | Jan 27, 2021 | May 27, 2021 | 1853 days past EOL | EOL |
| 2.2 | 2.2.0 | Mar 18, 2021 | Aug 6, 2021 | 1782 days past EOL | EOL |
| 2.3 | 2.3.0 | May 27, 2021 | Nov 25, 2021 | 1671 days past EOL | EOL |
| 2.4 | 2.4.0 | Aug 6, 2021 | Jan 31, 2022 | 1604 days past EOL | EOL |
| 2.5 | 2.5.0 | Nov 25, 2021 | May 5, 2022 | 1510 days past EOL | EOL |
| 2.6 | 2.6.1 | Jan 31, 2022 | Aug 10, 2022 | 1413 days past EOL | EOL |
| 2.7 | 2.7.1 | May 5, 2022 | Dec 9, 2022 | 1292 days past EOL | EOL |
| 2.8 | 2.8.2 | Aug 10, 2022 | Mar 9, 2023 | 1202 days past EOL | EOL |
| 2.9 | 2.9.3 | Dec 9, 2022 | Jun 22, 2023 | 1097 days past EOL | EOL |
| 2.10 | 2.10.1 | Mar 9, 2023 | Sep 28, 2023 | 999 days past EOL | EOL |
| 2.11 | 2.11.2 | Jun 22, 2023 | Jan 18, 2024 | 887 days past EOL | EOL |
| 2.12 | 2.12.1 | Sep 28, 2023 | Apr 25, 2024 | 789 days past EOL | EOL |
| 2.13 | 2.13.1 | Jan 18, 2024 | Aug 1, 2024 | 691 days past EOL | EOL |
| 2.14 | 2.14.1 | Apr 25, 2024 | Nov 7, 2024 | 593 days past EOL | EOL |
| 2.15 | 2.15.1 | Aug 1, 2024 | Apr 7, 2025 | 442 days past EOL | EOL |
| 2.16 | 2.16.1 | Nov 7, 2024 | Oct 8, 2025 | 258 days past EOL | EOL |
| 2.17 | 2.17.3 | Apr 7, 2025 | Feb 2, 2026 | 141 days past EOL | EOL |
| 2.18 | 2.18.3 | Oct 8, 2025 | Jun 1, 2026 | 22 days past EOL | EOL |
| 2.19 | 2.19.0 | Feb 2, 2026 | TBD | Supported | Active |
| 2.20 | 2.20.1 | Jun 1, 2026 | TBD | Supported | Active |
What does KEDA end of life mean for your organization?
When a version of KEDA reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL KEDA should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL KEDA versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →