This looks really cool! Hopefully it scratches the same itch docker-compose did a long time ago, but for those running Kubernetes.<p>I was just talking to a coworker this morning about how Helm is great, but its very analogous to debs or rpms: You would use it all day to install core-libraries (or services for k8s) on your system (or cluster), but probably not your first choice for shipping your business application.<p>I know, with Helm you can update a value for an image of a "release" (Helm term for an installed chart): but you hand off the upgrade of the application to the Tiller server to manage. If anything in your deployment goes south, Kubernetes will just keep trying to push it out until it works or is manually rolled back. Until Kubernetes gets automated rollbacks (<a href="https://github.com/kubernetes/kubernetes/issues/23211" rel="nofollow">https://github.com/kubernetes/kubernetes/issues/23211</a>), this can be less than ideal.<p>Going with the rpm/deb analogy, I prefer to use something that would take the place of Puppet/Ansible (like Spinnaker) for _my_ applications I release, and still use Helm for the cluster level services like monitoring, logging, etc.