argocd-vault-plugin
argocd-vault-plugin copied to clipboard
Describe how to not loose helm functionality when using this plugin
Is your feature request related to a problem? Please describe.
When I am using a cluster with argocd to play around and test something, often I will use argocd in full-gui mode : point, click, add helm repo, enter the values into the boxes, become frustrated that someone hasn't set default values in the values.yaml
file and have to enter it into the text box for values, and iterate.
A lot of the above is actually missing if you want to use helm with vault-plugin because argocd doesn't know that you're using helm.
I am pretty sure I can fight my way through and make it work by modifying the docker image so that helm
is a script that calls the real helm template command and pipes it to the plugin, but that's a lot of work and really not documented.
Describe the solution you'd like A document to follow for enabling the plugin in a way that doesn't remove functionality from argocd when using helm charts.
Describe alternatives you've considered replacing the helm binary in the image.
Hi - if I understand you right, you seek a way to be able to manipulate the values files/explicitly set values that an Argo app using Helm + AVP is deployed with, from the Argo CD UI. I don't know if this is possible, b/c as I understand it, the Argo CD UI is able to provide the "Helm values form" because of the helm
key in the Argo app manifest, which isn't and cannot be used in conjunction with a config management plugin like AVP because of how Argo CD works.
@jkayani is correct there is really nothing we can do about that. As you can see in this issue https://github.com/argoproj/argo-cd/issues/7623 it’s a known problem. We just combat this by formatting the plugin to take advantage of Helm arguments and be as like the native Helm support https://argocd-vault-plugin.readthedocs.io/en/stable/usage/#with-helm
One of the reasons I worded the ticket as "describe how to" rather than a bug report/feature asking for the functionality to be restored is because I guessed that it was the architecture of argocd that is in the way here. It should however be possible to get this functionality working by running as a wrapper for helm in the same way as described here rather than as a real plugin. I have not yet spent the time to do so but the idea would be to add it to the documentation so people know that it's an option.
I've been working on a separate project to do this. We use argocd helm applications all the time with avp and kustomize.
https://github.com/teejaded/helm-wrap/tree/examples/examples/avp-kustomized-helm