chef infra client end of life dates — full support timeline
8 of 10 tracked chef infra client 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 |
|---|---|---|---|---|
| 19 | 2026-02-05 | not announced | 19.3.15 | supported |
| 18 | 2022-09-28 | not announced | 18.11.11 | supported |
| 17 | 2021-04-27 | 2026-02-05 | 17.10.163 | ended |
| 16 | 2020-04-27 | 2022-11-30 | 16.18.30 | ended |
| 15 | 2018-10-26 | 2020-12-19 | 15.17.4 | ended |
| 14 | 2018-01-22 | 2020-01-21 | 14.15.6 | ended |
| 13 | 2017-03-01 | 2018-10-26 | 13.12.14 | ended |
| 12 | 2014-11-25 | 2018-01-22 | 12.22.5 | ended |
| 11 | 2013-02-01 | 2017-03-01 | 11.18.12 | ended |
| 10 | 2012-06-18 | 2014-12-03 | 10.34.6 | ended |
Who is affected
Anyone running an unsupported chef infra client 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/chef-infra-client, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next chef infra client deadline
You are reading this because a chef infra client 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 chef infra client and related deadline as it is announced, with exact dates and primary sources.
Watch chef infra client deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.