Repository navigation
ArgoCD to deploy a upstream(bitnami) chart. Values.yml do not apply config #5881
|
Hi, I am running Argocd 2.0 and bitnami/kube-prometheus chart. This is my private git repo structure: dependencies:
|
Replies: 1 comment 1 reply
|
Without seeing your When Helm is rendering a dependency, it will require the dependencies' values to be provided below the dependency's name as key, so that Helm will know which part of the So, in order to provide the values to a dependency named foo: bar
bar:
foo: barit should be stored in your kube-prometheus:
foo: bar
bar:
foo: barHTH. |
Without seeing your
values.yamlI can just guess here that you might be using a verbatim version ofvalues.yamlfor thekube-prometheusstack.When Helm is rendering a dependency, it will require the dependencies' values to be provided below the dependency's name as key, so that Helm will know which part of the
values.yamlto pass to the dependency when rendering.So, in order to provide the values to a dependency named
kube-prometheusand given your originalvalues.yamlbe likeit should be stored in your
values.yamllike the following instead:HTH.