Too little, too late. Surpassed by Ansible (and AWX) a long time ago. Chef was nice in 2014 to get rid of puppet...
But chef is a completely different beast. For those who can digest ruby (as I do), chef is still a fantastic choice. I have fond memories of chef. Written countless cookbooks, recipes and bootstrapped thousands of machines with it. Having full power of ruby at one’s disposal can’t be underestimated. But one has to appreciate ruby first ;)
That's when your config becomes unmaintainably large and complicated with personal taste.
The soup of the Chef ecosystem has always seemed hard to understand (and teach new team members): Chef, Chef-solo/zero, rubocup, test kitchen, food critic, berkshelf automate, delivery druck, inspec, infa, etc...
With containers and immutable infrastructure there just isn't the need anymore. They obviously realized this and created Habitat as a response, but after trying it a few times, I don't see why I'd use it over plain old Docker + K8s.
If you still need configuration management, Ansible is more flexible, is easier to learn/teach (no need to learn Ruby), agentless, no need to run a sever and can also do some orchestration.
Instead we'll just learn yet another ad-hoc language clumsily built atop YAML, and put up with Norway always being false when abbreviated. :)
"no"
Isn't that just, Docker?
It's an entire CI/CD environment with containers, including orchestration of updates, the ability to do an immutable infrastructure, and so much more.