-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helm parameters should allow maps #3936
Comments
I think this is an Argo CD issue, not an Argo Workflows issue? |
+1 On this one.. Currently the HELM charts look like this when u try to provision your own values. Current declaration looks like this:
Proposal would be to allow the mapping values too:
Adding to what @sfxworks said, this looks the same but it makes it easier:
We can see similar design in the HelmRelease CRD used in the Helm-Operator (Flux). |
duplicate #2936 . I'm really missing this feature too though |
Closing in favor of duplicate #2936 |
Summary
Helm parameters should allow for map values instead of just strings
Motivation
Trying to configure annotations for ingress https://github.com/goharbor/harbor-helm/blob/master/values.yaml#L37-L40
Using application spec https://argoproj.github.io/argo-cd/operator-manual/declarative-setup/
May need to use values.yaml. In which case, the ability to have secrets referenced in parameters would also be nice
Proposal
Unknown but adjustments may be needed to CRD at the least.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: