calico end of life dates — full support timeline
6 of 8 tracked calico 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 |
|---|---|---|---|---|
| 3.32 | 2026-04-30 | not announced | 3.32.1 | supported |
| 3.31 | 2025-10-21 | not announced | 3.31.6 | supported |
| 3.30 | 2025-05-05 | 2026-04-30 | 3.30.7 | ended |
| 3.29 | 2024-10-29 | 2025-10-21 | 3.29.7 | ended |
| 3.28 | 2024-05-10 | 2025-05-05 | 3.28.5 | ended |
| 3.27 | 2023-12-15 | 2024-10-29 | 3.27.5 | ended |
| 3.26 | 2023-05-27 | 2024-05-11 | 3.26.5 | ended |
| 3.25 | 2023-01-11 | 2023-12-15 | 3.25.2 | ended |
Who is affected
Anyone running an unsupported calico 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/calico, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next calico deadline
You are reading this because a calico 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 calico and related deadline as it is announced, with exact dates and primary sources.
Watch calico deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.