helmsman VS helm-controller

We've been using Helmsman (https://github.com/Praqma/helmsman) for the same use case. It supports some other creature comforts (automatic fetching of parameters from AWS SSM, chart ordering, etc.) and seems a bit more mature.

I've been using https://github.com/Praqma/helmsman for quite a few years now. Very pleased with it.

Have you looked at https://github.com/Praqma/helmsman ?

Kustomize manifests. Each microservice in its own folder. We have around 10 microservices, so it works for us. Db/metrics/monitoring/operators go into a Helmsman file.

I'm using Helmsman. It's a wrapper around Helm that allows you to inject environmental variables, amongst other things. It allows me to easily inject environmental variables from my Gitlab CI/CD into my Helm release.

Here's some issues where people asked the same question: https://github.com/Praqma/helmsman/issues/18 https://github.com/roboll/helmfile/issues/240

If you're using helm I believe the helm controller could help you here

I agree with Helm Operator, though it is in maintenance mode and on the cusp of replacement with a newer tool. I'm working with FluxCD org now, on the next generation of Helm Operator, check out Helm Controller, under the new Flux2 which is rapidly approaching 100% feature parity (in the sense of approaching a limit, it is for almost all use cases 100% feature parity already) with the stable Flux v1 + Helm Operator.