April was a big month for us at Chef. During this month we released Chef 14, a friendlier easier Chef. With more than 30 new resources added, this is, by far the fastest and easiest to use, Chef version yet. Today (April 30th) marks another important milestone with the End of Life for Chef 12, which means there will be no future feature release or security updates to this version of the Chef Client. You can learn more about both these milestones on Julian Dunn’s blog post here.
For customers using OpsWorks for Chef Automate if you are still on Chef 12 this means a lot more than merely using and end of life version of Chef Client. While these old Chef 12 clients talk to the Chef Server, customers aren’t benefiting from several high value functionality such as Compliance that customers of OpsWorks for Chef Automate get to use. Customers also benefit from closing the security vulnerabilities (the Chef Client has newer versions of Ruby, RubyGems and other dependencies) and the additional resources as well as additional properties of existing resources.
OpsWorks for Chef Automate provides customers a fully managed Chef Automate infrastructure. In this blog post on the AWS Management Tools Blog, Darko Meszaros takes you through a step-by-step process to upgrade your Chef Client including things to consider when planning your upgrade.
- Read the AWS blog post: Updating chef-client on AWS OpsWorks for Chef Automate nodes
- Learn what’s new in Chef Client 14
- Learn how to manage your first node, test Chef cookbooks on temporary cloud instances, and deploy changes to a production-like environment, all on AWS