This article is based on reporting originally published by SiliconAngle, covering announcements made at Chef’s annual developer conference in May 2018.
The Core Problem: Speed vs. Quality in DevOps Pipelines
DevOps exists to accelerate the delivery of infrastructure and application changes while maintaining quality and policy compliance. In practice, that balance is difficult to strike. According to a survey conducted by Chef Software at the time of these announcements, nearly three-quarters of DevOps professionals identified “time from code to production” and “time from commit to deploy” as their most important operational metrics. Yet a majority of those same respondents reported spending days, weeks, or even months completing application builds, deployments, and compliance verifications.
The conclusion is straightforward: manual processes cannot meet modern delivery expectations. Achieving meaningful velocity requires automation — and automation, in turn, demands tooling that is visual, flexible, and capable of spanning heterogeneous cloud environments at scale.
Chef’s Position in the DevOps Ecosystem
Chef Software is one of the longer-standing DevOps automation vendors, with its open-source configuration-management codebase dating back nearly a decade before these announcements. Chef’s domain-specific language (DSL) allows engineers to write declarative system configuration instructions called recipes, which are grouped into reusable cookbooks. These abstractions let teams automate provisioning and verification across a wide range of cloud platforms, including:
- Amazon EC2
- Google Cloud Platform
- Microsoft Azure
- Oracle Cloud
- OpenStack
- IBM SoftLayer
- Rackspace
By the time of these announcements, Chef claimed more than a thousand users worldwide for its continuous automation solutions across cloud-native environments.
What Chef Announced: Four Core Capabilities
At its 2018 annual developer conference, Chef introduced significant additions across its solution portfolio. The announcements addressed four distinct areas of the DevOps workflow:
1. Chef Workstation: Agentless, Ad-Hoc Automation
The new Chef Workstation replaced and extended the earlier ChefDK bundle. Its defining new capability is an agentless execution model: DevOps practitioners can run recipes and entire cookbooks remotely on target nodes without requiring a Chef agent to be installed on those nodes. This is delivered through a new “target mode” that executes configuration tasks directly from the engineer’s desktop or laptop.
The workstation integrates with Chef’s flagship Automate platform, meaning ad-hoc tasks completed locally can feed back into the centralized pipeline. This architectural shift toward agentless operation brings Chef closer in design to tools like Red Hat’s Ansible, which has long operated without requiring agents on managed nodes.
2. Chef Automate 2.0: Unified, Microservices-Based Dashboard
Chef Automate 2.0 introduced a rebuilt architecture designed for scale and flexibility. Key characteristics include:
- A Go-based microservices backend replacing the prior monolithic architecture
- A REST API-driven web UI for faster, more flexible interaction
- Streaming ingestion and visualization of infrastructure and compliance data across tens of thousands of nodes from a single installation
- Closed-loop release-pipeline automation combining deployment orchestration with compliance verification
- In-place upgrade support for Automate 1.0 customers, with automatic migration of historical data
The 2.0 release represents a significant internal rewrite. Teams operating at scale should evaluate the microservices architecture carefully, particularly around operational complexity and resource requirements compared to 1.0.
3. Chef Habitat: Kubernetes Operator and Multi-Cloud Application Delivery
Chef Habitat, the application automation component of the Automate platform, received substantial Kubernetes-focused enhancements:
- An updated Kubernetes Operator for orchestrating Habitat-packaged applications on Kubernetes clusters
- Support for exporting Helm charts for complex, multi-service Kubernetes applications
- Integration with the Open Service Broker API, enabling standardized service provisioning across cloud platforms
- Export of containerized applications to Azure Kubernetes Service (AKS)
- On-premises (behind-the-firewall) deployment support
- Integration with Splunk for storing and analyzing application-release operational data
These additions position Habitat as a tool capable of managing the full application lifecycle — from build and packaging through deployment and ongoing operational monitoring — across both public cloud Kubernetes services and private infrastructure.
4. Chef InSpec: Compliance Verification Across Clouds and Edge Devices
Chef InSpec, the compliance automation component, extended its platform coverage significantly:
- Native automated verification of AWS and Microsoft Azure policies, with Google Cloud Platform support available in beta at the time of announcement
- Built-in compliance scanning for 30 new target types, including Cisco IOS network devices operating as agentless targets
- Enhanced API-based compliance scanning and reporting in AWS, Azure, and GCP on both ad-hoc and scheduled bases
The addition of Cisco IOS as an agentless compliance target is notable: it extends policy verification beyond traditional compute infrastructure to network layer devices, which are increasingly relevant to security and compliance postures in hybrid environments.
Competitive Context: A Crowded and Consolidating Market
Chef’s architectural move toward agentless execution with Workstation narrowed one historical gap with Red Hat’s Ansible. However, the broader competitive picture for Chef — and its traditional rival Puppet — was already challenging in 2018. Larger, more diversified vendors including Red Hat, IBM, Microsoft, and HPE were building or acquiring mature automation tooling integrated into broader hybrid-cloud and Kubernetes portfolios.
Chef’s strength remained in its mature DSL, its large cookbook ecosystem, and its compliance-as-code approach via InSpec. Its challenge was proving that a standalone automation specialist could remain relevant as cloud platform vendors embedded configuration management and deployment automation directly into their own managed services.
This dynamic has continued to evolve: in 2020, Chef Software was acquired by Progress Software, a shift that significantly changed its go-to-market trajectory.
Key Takeaways for DevOps Engineers
- Agentless execution matters for large, heterogeneous environments where managing agents introduces operational overhead — Chef Workstation’s target mode addresses this directly.
- Kubernetes operator support in Habitat is relevant if your team already uses Chef tooling and wants a consistent automation surface across containerized and non-containerized workloads.
- InSpec’s compliance-as-code model remains one of Chef’s most durable contributions: expressing compliance requirements as testable, version-controlled code is a practice worth adopting regardless of what other tooling you use.
- Helm chart export from Habitat reduces the friction of moving between Chef-native packaging and the Kubernetes ecosystem’s dominant package management format.