etcd end of life dates — full support timeline
5 of 8 tracked etcd 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.7 | 2026-07-08 | not announced | 3.7.1 | supported |
| 3.6 | 2025-05-15 | not announced | 3.6.14 | supported |
| 3.5 | 2021-06-15 | 2027-07-08 | 3.5.33 | supported |
| 3.4 | 2019-08-30 | 2026-06-01 | 3.4.45 | ended |
| 3.3 | 2018-02-01 | 2021-10-15 | 3.3.27 | ended |
| 3.2 | 2017-06-09 | 2021-03-28 | 3.2.32 | ended |
| 3.1 | 2017-01-20 | 2018-10-10 | 3.1.20 | ended |
| 3.0 | 2016-06-30 | 2017-01-20 | 3.0.17 | ended |
Who is affected
Anyone running an unsupported etcd 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/etcd, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next etcd deadline
You are reading this because a etcd 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 etcd and related deadline as it is announced, with exact dates and primary sources.
Watch etcd deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.