Knative End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Knative versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 0.13 | 0.13.3 | Mar 3, 2020 | Aug 18, 2020 | 2182 days past EOL | EOL |
| 0.14 | 0.14.3 | Apr 14, 2020 | Sep 29, 2020 | 2140 days past EOL | EOL |
| 0.15 | 0.15.0 | May 26, 2020 | Nov 10, 2020 | 2098 days past EOL | EOL |
| 0.16 | 0.16.0 | Jul 7, 2020 | Dec 22, 2020 | 2056 days past EOL | EOL |
| 0.17 | 0.17.1 | Aug 18, 2020 | Feb 2, 2021 | 2014 days past EOL | EOL |
| 0.18 | 0.18.2 | Sep 29, 2020 | Mar 16, 2021 | 1972 days past EOL | EOL |
| 0.19 | 0.19.0 | Nov 10, 2020 | May 18, 2021 | 1909 days past EOL | EOL |
| 0.20 | 0.20.0 | Jan 12, 2021 | Jun 29, 2021 | 1867 days past EOL | EOL |
| 0.21 | 0.21.0 | Feb 23, 2021 | Aug 10, 2021 | 1825 days past EOL | EOL |
| 0.22 | 0.22.0 | Apr 6, 2021 | Sep 21, 2021 | 1783 days past EOL | EOL |
| 0.23 | 0.23.0 | May 18, 2021 | Nov 2, 2021 | 1741 days past EOL | EOL |
| 0.24 | 0.24.0 | Jun 29, 2021 | Dec 14, 2021 | 1699 days past EOL | EOL |
| 0.25 | 0.25.0 | Aug 10, 2021 | Jan 25, 2022 | 1657 days past EOL | EOL |
| 0.26 | 0.26.1 | Sep 21, 2021 | Mar 8, 2022 | 1615 days past EOL | EOL |
| 1.0 | 1.0.2 | Nov 2, 2021 | Apr 19, 2022 | 1573 days past EOL | EOL |
| 1.1 | 1.1.4 | Dec 14, 2021 | May 31, 2022 | 1531 days past EOL | EOL |
| 1.2 | 1.2.5 | Jan 25, 2022 | Jul 12, 2022 | 1489 days past EOL | EOL |
| 1.3 | 1.3.2 | Mar 8, 2022 | Aug 30, 2022 | 1440 days past EOL | EOL |
| 1.4 | 1.4.0 | Apr 19, 2022 | Oct 11, 2022 | 1398 days past EOL | EOL |
| 1.5 | 1.5.1 | May 31, 2022 | Nov 29, 2022 | 1349 days past EOL | EOL |
| 1.6 | 1.6.3 | Jul 12, 2022 | Jan 10, 2023 | 1307 days past EOL | EOL |
| 1.7 | 1.7.4 | Aug 23, 2022 | Feb 21, 2023 | 1265 days past EOL | EOL |
| 1.8 | 1.8.6 | Oct 18, 2022 | May 2, 2023 | 1195 days past EOL | EOL |
| 1.9 | 1.9.4 | Jan 24, 2023 | Aug 1, 2023 | 1104 days past EOL | EOL |
| 1.10 | 1.10.6 | Apr 25, 2023 | Oct 31, 2023 | 1013 days past EOL | EOL |
| 1.11 | 1.11.6 | Jul 25, 2023 | Jan 30, 2024 | 922 days past EOL | EOL |
| 1.12 | 1.12.4 | Oct 24, 2023 | Apr 30, 2024 | 831 days past EOL | EOL |
| 1.13 | 1.13.2 | Jan 23, 2024 | Jul 22, 2024 | 748 days past EOL | EOL |
| 1.14 | 1.14.2 | Apr 23, 2024 | Oct 22, 2024 | 656 days past EOL | EOL |
| 1.15 | 1.15.3 | Jul 23, 2024 | Jan 21, 2025 | 565 days past EOL | EOL |
| 1.16 | 1.16.3 | Oct 22, 2024 | Apr 22, 2025 | 474 days past EOL | EOL |
| 1.17 | 1.17.2 | Jan 28, 2025 | Jul 28, 2025 | 377 days past EOL | EOL |
| 1.18 | 1.18.2 | Apr 22, 2025 | Oct 28, 2025 | 285 days past EOL | EOL |
| 1.19 | 1.19.9 | Jul 22, 2025 | Feb 3, 2026 | 187 days past EOL | EOL |
| 1.20 | 1.20.3 | Oct 21, 2025 | May 5, 2026 | 96 days past EOL | EOL |
| 1.21 | 1.21.3 | Jan 27, 2026 | Aug 4, 2026 | 5 days past EOL | EOL |
| 1.22 | 1.22.1 | Apr 28, 2026 | Nov 3, 2026 | 86 days remaining | Warning |
| 1.23 | 1.23.0 | Jul 28, 2026 | Feb 2, 2027 | 177 days remaining | Warning |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/knative)
What does Knative end of life mean for your organization?
When a version of Knative 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 Knative 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.
Your options when Knative reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Knative versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Knative has 36 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Knative exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.