hashicorp / hashicorp/vault-secrets-operator
Allow mTLS between VSO and external Vault instance
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 601
- Forks
- 145
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 6
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the annotation handling and external Vault connection entry points in the operator, then trace how referenced Kubernetes Secrets are currently processed. Done means a documented annotation-based way to provide the client certificate and private key, with coverage showing that an external Vault mTLS connection succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100