Ohai Chefs! We’ve just released Chef Client 12.3.0. This release includes bug fixes as well couple of new goodies… we hope you enjoy them. You can check out the CHANGELOG for a full set of the changes.

Note: This post originally appeared on Padgeblog. Chef-vault is a tool created by Nordstrom and adopted by Chef as the de facto way to handle secrets management using the Chef platform. Chef-vault builds on the original Chef encrypted data bags concept¹.

On Friday, April 17th Hosted Chef experienced an average error rate of approximately 30% for a period of 4 hours followed by intermittent brief periods of similar error rates until April 22nd.

In philosophy, ontology is (as Wikipedia says) “the study of what entities exist or can be said to exist, and how such entities can be grouped, related within a hierarchy, and subdivided according to similarities and differences.

This is an updated version of the previous post from August, 2014: Getting started with oc-id and Supermarket Chef Server 12 includes oc-id, the OAuth2 service that powers id.chef.io. After upgrading to this release, Chef customers can now run their own Supermarket service behind a firewall.

Ohai Chefs! Chef Server 12.0.8 and Enterprise Chef 11.3.1 are available for immediate download. This release addresses the following vulnerabilities: CVE-2013-2028 CVE-2013-4547 CVE-2014-0088 CVE-2014-0133 CVE-2014-3556 CVE-2014-3616 This corresponds to chef-server issue 142, “Update Embedded Openresty NGINX”. Additional Changes Chef Server 12.0.8 has been further updated as follows: The Chef Server 12.0.

This is a guest post by Jon Rooney, Director of Developer Marketing at Splunk Two weeks ago at ChefConf, the Chef team announced an integrated app for Splunk to gain real-time insights from your Chef infrastructure.

Ohai Chefs, One of the exciting features in Chef Analytics 1.1.2 that is the ability to link Chef Analytics to Splunk. This features give you the ability to extract meaningful insights about your Chef infrastructure if you are using Splunk.

Starting with the Chef 12.2.0 Client there is no longer any need to use the validation key to provision new chef nodes with knife. Furthermore, all that needs to be done to take advantage of this feature is to delete your validation keys and optionally remove the validator configuration from your knife.rb file.