Skip to content
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

feat: initialize and unseal vault after a crash #42

Open
venkatamutyala opened this issue Jun 4, 2023 · 0 comments
Open

feat: initialize and unseal vault after a crash #42

venkatamutyala opened this issue Jun 4, 2023 · 0 comments

Comments

@venkatamutyala
Copy link
Contributor

venkatamutyala commented Jun 4, 2023

As a System Administrator, I want hashicorp vault to initialize itself after cluster bootstrap and i want it to be unsealed after a vault pod crashes because I don't want to have to manually intervene when it happens.

Acceptance Criteria:

  • Do not leverage kms unseal options that are cloud-specific as this creates cloud-specific lock-in (something we want to avoid)
  • Have an app that unseals the vault and stores the unseal keys into the tenant S3 bucket
  • Have the same app, or another service that leverages the unseal keys from the tenant s3 bucket to unseal the vault store after any vault pods crash.
  • Add back to this repo as an ArgoCD application
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant