Chef vs Puppet vs Ansible: Why I Stopped Picking a Team
I’ve shipped production config changes through Chef, Puppet, and Ansible, at different employers, in different decades of my career, and I have never once seen any of the three camps fully convince the others of anything in a Slack/Teams thread.
Chef people will tell you that treating infrastructure as actual testable, versionable code — recipes, cookbooks, the whole Ruby-flavored apparatus — is the “real” engineering approach, and if you enjoy writing infrastructure the way you write application code, they have a point.
Puppet people will tell you declarative, agent-based configuration management is the mature, battle-tested way to keep fleets of servers in a known state, and they’re not wrong either.
Ansible people will tell you agentless, push-based simplicity means you can get something running in twenty minutes instead of two days of setting up an agent architecture, and they’re also not wrong.
This is the most Canadian argument in infrastructure: all three sides are being reasonable and somehow that makes it worse.
Get Gurpreet Singh Kambo’s stories in your inbox
Join Medium for free to get updates from this writer.
What twenty-two years of picking sides depending on the job actually taught me: the tool matched the problem, not the trend.
Chef made sense on a team that already thought like software engineers and wanted config management to feel like writing tests.
Puppet made sense for a large, stable fleet of long-lived servers with real drift-management needs.
Ansible made sense when I needed fifteen ephemeral cloud instances configured by Thursday and didn’t have time to argue about it.
I’ve used all three where each one made sense, and the one time I tried to force one tool into another’s job out of sheer personal loyalty, I regretted it by the following Monday.
Loyalty to a specific tool is a personality trait. It is not an architecture decision.
Chef, Puppet, or Ansible — and be honest about whether that’s a technical opinion or just muscle memory from your first job.
Connect with me on LinkedIn — two decades of DevOps and multi-cloud strategy, $3M in FinOps wins, and a track record of shipping through real fires, real deadlines, and real 2 AM PagerDuty alerts: linkedin.com/in/gurpreetsinghkambo
