-
Notifications
You must be signed in to change notification settings - Fork 190
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
argocd-vault-plugin (sidecar) not updating secret value #591
Comments
You can’t use built in helm with a cmp. Remove this
|
well, that sucks. That value consists of my overrides and its not a small file. The deployment/configuration for AVP seems overly complex. I wanted to use this because it seemed simple enough to add an inline parameter to pull secrets from a secret store, vs an operator that will just create the secret object. Might have to look at another path. |
https://argocd-vault-plugin.readthedocs.io/en/stable/usage/#with-helm You can still use a values file, just have to specify it as an env and use that in your template command.
|
can this also work with using multiple resources like this?
|
Last I checked no argoproj/argo-cd#11814 but you might want to check with Argo CD to see if that has changed |
I installed argocd-vault-plugin via sidecar and I am having trouble and getting a test secret in my cluster to update with the credentials that live in vault. The AVP container is coming up and it seems that things are healthy and running.
Vault was installed as HA with TLS enabled.
I installed argocd via Helm, and the argocd-apps via helm as well.
This is what I have for my repoServer:
Here is my cmp definition
Here is the application CRs for argocd
secret container vault configuration for argo
Test secret
When I run
argocd-vault-plugin generate . -s argocd-vault-plugin-credentials
within the avp container, this is what I get returned:I guess this is a good sign?
So I think overall my configuration looks correct, but the test secret deployed with argo is not updating the secret value in the k8s secret.
The text was updated successfully, but these errors were encountered: