Hacker News Reader

Comment by tuunit | Hacker News Reader

A docker-compose like tool for multi helm chart deployment handling. Primarily meant to be used for development, to be able to quickly deploy all dependent services and tools from within a single yaml file.

View on HN

How does it differ from Helm? Templating resources and sub-charts is already what Helm does.

First and for most you can only have one sub chart layer in helm. So if you want to setup a full environment replica on your local machine using your production helm charts, which might already have chart dependencies you cannot use another wrapper helm chart at the top. As helm does not have sub-sub-dependency / recursive resolution. Furthermore, helm compose allows for FULL configuration as code. With helm you always have define some parameters in the command line like the correct namespace, release name and chart name and chart version with helm compose you just write: "helm compose up". Obviously, that can be solved by aliases but this way truly everything is kept inside a configuration file.

> First and for most you can only have one sub chart layer in helm

I don't think that's true?

the request for this feature has been open since 2017: https://github.com/helm/helm/issues/2247

It's related but I don't think it prevents you from having nested dependencies.

This is about building packaged charts with multiple levels in one go (e.g. without packaging the nested ones first).

Reply on news.ycombinator.com