kyverno end of life dates — full support timeline
8 of 11 tracked kyverno releases have already reached end of life. The dates below are published support dates, not estimates.
Version support timeline
| Release | Released | End of life | Latest | Status |
|---|---|---|---|---|
| 1.18 | 2026-04-29 | not announced | 1.18.2 | supported |
| 1.17 | 2026-02-02 | not announced | 1.17.2 | supported |
| 1.16 | 2025-11-10 | not announced | 1.16.4 | supported |
| 1.15 | 2025-07-31 | 2026-04-29 | 1.15.20 | ended |
| 1.14 | 2025-04-24 | 2026-02-02 | 1.14.5 | ended |
| 1.13 | 2024-10-29 | 2025-11-10 | 1.13.6 | ended |
| 1.12 | 2024-04-26 | 2025-07-31 | 1.12.7 | ended |
| 1.11 | 2023-11-10 | 2025-04-25 | 1.11.5 | ended |
| 1.10 | 2023-05-30 | 2024-10-29 | 1.10.7 | ended |
| 1.9 | 2023-02-01 | 2024-04-26 | 1.9.5 | ended |
| 1.8 | 2022-10-10 | 2023-11-10 | 1.8.5 | ended |
Who is affected
Anyone running an unsupported kyverno release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.
Source
These dates are maintained by endoflife.date/kyverno, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next kyverno deadline
You are reading this because a kyverno release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every kyverno and related deadline as it is announced, with exact dates and primary sources.
Watch kyverno deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.