What’s the best way to manage Helm charts?

Category: Deployment, Kubernetes, Docker, Infrastructure, github

You can use it in many different ways which is great, but can also be overwhelming.

In one of our projects, we started out with a large chart that was used to deploy multiple services.

In this case, it makes sense to store the Helm chart in a chart repository such as ChartMuseum.

It’s much easier to test for these kinds of issues if the chart and the code are in the same repo and can be tested in the same branch.

If you apply this practically to Helm chart maintenance and infrastructure configuration in general, you would put much of the responsibility in the hands of application developers.