Hey all! I’m trying to setup a gitops solution based on helm. All of my yamls are in a monorepo, and I'm not building any charts manually using

helm dependency build

or any other helm command. In my solution I will need nested dependencies to be resolved automatically, as I want several layers of values (with overrides for each layer) For example:

/clusters/01/Chart.yaml

will have a dependency of

/environments/prod

/environments/prod/Chart.yaml

will have a dependency of

/region/US

/region/US/Chart.yaml

will depend on an "umbrella" chart, that this umbrella chart will deploy all apps, while overriding the values according to the precedence of the dependencies. Using helm in Flux/ArgoCD, I was not able to do that as helm doesn't support recursive dependency building, so only the first 2 charts were deployed. I tried using basic helmfile examples, but the same limitation still in place. I wonder if I can somehow leverage helmfile to dynamically resolve all nested dependencies of an helm chart without having to commit all charts'

tgz

files?

Generally you specify the needs https://helmfile.readthedocs.io/en/latest/#dag-aware-installationdeletion-ordering-with-needs

Thanks! So basically it will create multiple releases, based on the

needs

ordering, and the chart

dependencies

are not needed anymore? The thing is that each dependency chart will hold its own values.yaml, which results in layers of overrides. Can multiple releases provide similar functionality of values overrides somehow?

Each environment can provide values overrides. The needs builds a graph and ensures everything gets installed in the correct order. The first thing we did was got rid of our umbrella charts and set up the needs correctly

Alex is correct: co-signed by a hellfire maintainer