hashicorp / hashicorp/vault-helm
Add an automatic init step
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 898
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Description
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
In production, you will never do any manual steps, not even a single one, then why do we always have to do an operator init. If we want an auto-unseal with KMS then there MUST be an option in helm charts to automatically init the vault, save the keys into KMS and unseal itself on day-zero.
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
The only solution is - Provide a helm value that says- automaticallyInit=true with KMS details.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
No alternative, software should be simple to use.
**Additional context**
Add any other context or screenshots about the feature request here.
Only context - whenever we need to provide delivery to any client, they need a single helm chart which consists of all the application charts and dependencies. They want to do only "HELM INSTALL" and nothing else. With this helm install, they want to install all the required applications with their dependencies.
Contributor guide
Research direction
Start by reviewing the Helm chart's values and the Vault initialization and auto-unseal flow, with particular attention to KMS configuration. Define the behavior required for a single Helm install to initialize Vault, store the keys in KMS, and unseal on day zero; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100