Open jannfis opened 4 years ago
The workaround is to either create the application declaratively or via the CLI.
Another workaround is to click the Edit as YAML
button in UI and specify the custom values files. Then the helm values field is correctly populated.
To add values file via GUI (declaratively), edit the app manifest:
project: project-name
source:
...
helm:
valueFiles:
- ./path/to/file
The path is relative to the dir where the main chart lives.
Other details about what's possible with values files here: https://github.com/argoproj/argo-cd/issues/938
Checklist:
argocd version
.Describe the bug
When using Helm charts stored in Git, one can specify a values file to use for parametrization. Sometimes, it's convenient to store all the values files in different directories outside of the chart's directory, i.e.
One can refer to this file as
../values/values.yaml
when the source path of the application ishelm-dependency-subdir/chart
, i.e:This works as expected:
However, when creating the app within the UI, specifying path
../values/values.yaml
results in the Helm values field being empty and no values to be used at all. No error message is displayed, and nothing is printed in the logs. The entered values files is just silently ignored.To Reproduce
https://github.com/jannfis/argocd-example-apps/helm-dependency-subdir/chart
in the web UI, specifying../values/values.yaml
for the Helm values to use.Expected behavior
Same behaviour as when the app would be created using the CLI: values file specified is taken into account when rendering manifests via Helm.
Version
Logs