Vault Integration with ArgoCD's cluster/repo secrets.

[rumstead]

I have gone through and read about secret management on the docs. I also saw the IBM secret plugin but I still need some clarity on somethings.

I want to be able to supply cluster and repository credentials via Vault, does anyone have any examples of doing this?

For the cluster secrets, I stumbled across execProviderConfig on the docs site. An off-the-cuff thought I had, was to use execProviderConfig to hit the Vault API and generate the config or even use the Vault init container to get the config and have a script via execProviderConfig effectively cat it.

For the repository credentials, there doesn't seem to be a way around using raw Kubernetes secrets? Is that an accurate statement? I could have Vault generate these either via kustomize secrets generator, etc etc.

Any examples or guidance you all have is greatly appreciated.