I am trying to use Helm (inside ArgoCD) to install dagster and dagster-user-deployments in kubernetes with Charts.yaml and seperate values.yaml files located in the same directory. Both Charts seem to be installing but the values.yaml files don't seem to be replacing the default values and still using the example code. I am using the files from the github repo and have tried many variations from full files to just whats needed. I can see the values being pulled in ArgoCD but they are not being used by dagster. I have several apps installed this same way and have no issues with them. I have a work around with embedding the values.yaml info in ArgoCD Application.yaml file but it would be more ideal to use the values.yaml files directly. Any ideas on what may cause the values.yaml to not be used? Your examples have Helm with a specified values.yaml file using the "-f" flag?

Could you show your

values.yaml

? One theory is that you mistyped the key in YAML

A little bit about my deployments. I have both dagster and dagster-user-deployments installed thru helm version 1.0.7. I have attached the full and minimal versions of the values.yaml files (without real environment info) I am using. I have noticed that even though I have explicitly set "enableSubchart: false" for dagster the Chart still installs the "k8s-example-user-code" when I use a separate values.yaml file. The file I provide is still being used as I can see my defined etl info inside helm parameters but for some reason it's not taking priority or being ignored. The only way I am able to get it working is to "embed the values.yaml info in my ArgoCD application.yaml file which is not ideal. I have many other application doing this same approach but they are working as expected using separate values.yaml files. Just not sure why the values.yaml files are not being used. Thanks for assistance

when you say

I can see the values being pulled in ArgoCD but they are not being used by dagster.

do you mean that in the Helm release, the values are taken up, but the default

k8s-example-user-code

still shows? Could you do a

helm show values

on your

dagster

and

dagster-user-deployments

to confirm? If that’s the case, then that’s definitely bug. If it isn’t the case, I think you’re running into a peculiarity with ArgoCD - I don’t have much experience with that system unfortunately.

Here is the values file from doing the command "

helm show values dagster/dagster > values.yaml

and then mocking it with my changes. This is for Dagster.

Hello, in fact, ArgoCD is not the problem as far as I remember but the way both helm charts are constructed. They are not really uncoupled. I end with redeploying everything with the main one.

Yes - I have to embed the values.yaml in the ArgoCD application.yaml for both the Dagster and Dagster-User-Deploy charts. I would prefer to have separate values.yaml but so far it's working nicely in Argo and I can apply updates to images rather easily

I would try for debugging reason

Have to try on a cluster without it maybe sometime this week.