Describe the bug
Though having the avp sidecar running and all variables set the desired variable is not fetched from vault.
When running sh manually in the avp sidecar the command argocd-vault-plugin generate secret.yaml times out.
When interactively shelling in the avp sidecar container and copying the secret.yaml there I tried the command argocd-vault-plugin generate secret.yaml which results in a timeout.
When simply asking argocd to apply the secret.yaml from git the secret is not fetched at all.
Screenshots/Verbose output
argocd-vault-plugin generate secret.yaml --verbose-sensitive-output
2023/12/20 08:08:49 reading configuration from environment, overriding any previous settings
2023/12/20 08:08:49 AVP configured with the following settings:
2023/12/20 08:08:49 avp_kv_version: 2
2023/12/20 08:08:49 Hashicorp Vault cannot retrieve cached token: stat /home/argocd/.avp/config.json: no such file or directory. Generating a new one
2023/12/20 08:08:49 Hashicorp Vault authenticating with Vault role argocd using Kubernetes service account token /var/run/secrets/kubernetes.io/serviceaccount/token read from ***
Error: context deadline exceeded
Usage:
argocd-vault-plugin generate <path> [flags]
Additional context
The installation of argo is called argocd-test and in namespace argocd-test to not interfere with the default installation on the cluster.
I tried playing around with the cluster role binding as mentioned in the docs somewhere but this didn't really help...
Hey guys,
thanks for the help in advance :)
Describe the bug Though having the avp sidecar running and all variables set the desired variable is not fetched from vault. When running sh manually in the avp sidecar the command
argocd-vault-plugin generate secret.yaml
times out.To Reproduce These are my configs:
Expected behavior For making sure my vault config is correct I added a deployment (see details) using the default agent-inject method → works.
When interactively shelling in the avp sidecar container and copying the
secret.yaml
there I tried the commandargocd-vault-plugin generate secret.yaml
which results in a timeout. When simply asking argocd to apply the secret.yaml from git the secret is not fetched at all.Screenshots/Verbose output
Additional context The installation of argo is called
argocd-test
and in namespaceargocd-test
to not interfere with the default installation on the cluster.I tried playing around with the cluster role binding as mentioned in the docs somewhere but this didn't really help...
Additionally, I tried with a vault token on root level and the token method → same issues.