-
Notifications
You must be signed in to change notification settings - Fork 102
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
Allow mTLS between VSO and external Vault instance #298
Comments
Hi @bbucko - Thanks for filing this issue, |
Hi, |
hey @bbucko did you get this resolved at last? |
Nah, we switched to a diffeent secrets management system. |
Hello 👋 I'm having the same issue. As mentioned |
Is your feature request related to a problem? Please describe.
Our instance of Vault is using mTLS and we are unable to private client cert/key. All attempts end up in 'remote error: tls: bad certificate'
Describe the solution you'd like
Set of annotations that would make it possible to provide reference to a secret containing private key/cert which would be used to establish mTLS connection with external instance of Vault.
Describe alternatives you've considered
Tried adding annotations (vault.hashicorp.com/tls-secret or vault.hashicorp.com/client-cert) but they are not working.
The text was updated successfully, but these errors were encountered: