In the documentation about CMP plugins via sidecar containers, it is recommended (or at least given as example) to use busybox as the image for your sidecar container. This should be changed imho, as this does not work properly if you are trying to install argocd-vault as a plugin. See also here: https://github.com/argoproj/argo-cd/issues/13539#issuecomment-1714696123
Motivation
A lot of people are using argocd-vault as a plugin. They should be provided with documentation that works out of the box for their usecase. It has to be an image that includes ca-certificates. Otherwise they will run into the following bug which I ran into myself:
Could not find secret: rpc error: code = Unavailable desc = connection error: desc = \"transport: authentication handshake failed: tls: failed to verify certificate: x509: certificate signed by unknown authority
Proposal
Update the documentation here and here to an image which includes ca-certificates. Or at least add a note for vault-plugin users.
Summary
In the documentation about CMP plugins via sidecar containers, it is recommended (or at least given as example) to use
busybox
as the image for your sidecar container. This should be changed imho, as this does not work properly if you are trying to install argocd-vault as a plugin. See also here: https://github.com/argoproj/argo-cd/issues/13539#issuecomment-1714696123Motivation
A lot of people are using argocd-vault as a plugin. They should be provided with documentation that works out of the box for their usecase. It has to be an image that includes
ca-certificates
. Otherwise they will run into the following bug which I ran into myself:Proposal
Update the documentation here and here to an image which includes
ca-certificates
. Or at least add a note for vault-plugin users.In the vault-plugin documentation they use a different image: https://argocd-vault-plugin.readthedocs.io/en/stable/installation/#initcontainer-and-configuration-via-sidecar