hashicorp / hashicorp/vault-helm
Separate Injector Vault namespace configurations for authentication and secrets endpoints
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 898
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Description
We would like to configure the authentication as much as possible in the injector setting (through Helm values), so that the service specific annotations would only include needed configuration for the secrets. The secret backend mounts will normally be deeper in the namespace structure than the auth mount.
As the configured namespace seems to get passed as HTTP header to all requests, there is no way to lock e.g. the auth URL to another namespace.
I guess there should be two configuration options. Also #752 might help a bit.
Contributor guide
Research direction
Start by reviewing the Helm values and injector configuration described in the issue, then read issue #752 for related context. Define the separate namespace settings needed for authentication and secrets endpoints, including how their HTTP headers should differ. Done means the chart exposes and documents both settings without requiring service-specific authentication configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100