EOL.Wiki EOL.Wiki
← ← Back to all products

Chef Infra Client

Active
DevOps & CI/CD Latest Version: 19.1.164 Latest Release: Feb 4, 2026

Chef Infra Client is an agent that runs on nodes to configure them according to Chef policies.

Versions

10

Latest Version

19.1.164

Active Support

1

EOL

8

Lifecycle Timeline

Today
19
19
18
18
17
17
16
16
15
15
14
14
13
13
12
12
11
11
10
10
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
19Feb 5, 2026YesNo19.1.164No
Active
18Sep 28, 2022Feb 5, 2026No18.9.4No
Security
17Apr 27, 2021Jan 10, 2022Feb 5, 202617.10.163No
EOL
16Apr 27, 2020Dec 19, 2020Nov 30, 202216.18.30No
EOL
15Oct 26, 2018Jan 21, 2020Dec 19, 202015.17.4No
EOL
14Jan 22, 2018Oct 26, 2018Jan 21, 202014.15.6No
EOL
13Mar 1, 2017Jan 22, 2018Oct 26, 201813.12.14No
EOL
12Nov 25, 2014Mar 1, 2017Jan 22, 201812.22.5No
EOL
11Feb 1, 2013Dec 3, 2014Mar 1, 201711.18.12No
EOL
10Jun 18, 2012Feb 1, 2013Dec 3, 201410.34.6No
EOL

Frequently Asked Questions

Which versions of Chef Infra Client have reached end of life?
The following Chef Infra Client versions have reached end of life and no longer receive security updates: 17, 16, 15, 14, 13, 12, 11, 10. It is recommended to upgrade to a supported version.
Is it safe to continue using Chef Infra Client 17?
Chef Infra Client 17 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Chef Infra Client?
The latest version of Chef Infra Client is 19.1.164, released in the 19 release cycle.
How many versions of Chef Infra Client are currently supported?
Chef Infra Client currently has 2 actively supported version(s): 19, 18.
When does Chef Infra Client 19 reach end of life?
Chef Infra Client 19 does not have a specific end-of-life date announced yet.
What should I do when Chef Infra Client reaches end of life?
When a Chef Infra Client version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.