hashicorp / hashicorp/vault-secrets-operator
Single secret to authenticate vault instead of per namespace
- Dominant language
- Go
- Stars
- 600
- Forks
- 146
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 6
Description
I've deployed VSO in it's own namespace & I've many different applications running in various namespaces.
I deployed VSS/VDS for each application in it's corresponding namespace along with the k8s-secret that authenticate vault to fetch the secret for the application
Now, instead of deploying k8-secret along with each VSS/VDS, can we have a single secret (with some labels/annotations) that we can add in a single namespace (maybe operator's namespace) & attach it to VSS/VDS in each namespace
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing how VSS/VDS resources currently reference the per-namespace Kubernetes Secret used to authenticate Vault. Determine whether one Secret in the operator namespace can be referenced safely by applications in other namespaces, and define the labels or annotations required. Done means the cross-namespace authentication behavior is specified and covered for the affected VSS/VDS resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100