cilium end of life dates — full support timeline
5 of 8 tracked cilium 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.20 | 2026-07-29 | not announced | 1.20.0 | supported |
| 1.19 | 2026-02-03 | not announced | 1.19.6 | supported |
| 1.18 | 2025-07-29 | not announced | 1.18.12 | supported |
| 1.17 | 2025-02-04 | 2026-07-29 | 1.17.18 | ended |
| 1.16 | 2024-07-24 | 2026-02-03 | 1.16.19 | ended |
| 1.15 | 2024-01-31 | 2025-07-29 | 1.15.19 | ended |
| 1.14 | 2023-07-27 | 2025-02-04 | 1.14.19 | ended |
| 1.13 | 2023-02-15 | 2024-07-24 | 1.13.18 | ended |
Who is affected
Anyone running an unsupported cilium 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/cilium, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next cilium deadline
You are reading this because a cilium 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 cilium and related deadline as it is announced, with exact dates and primary sources.
Watch cilium deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.