-
Notifications
You must be signed in to change notification settings - Fork 22
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
More options to configure unsealConfig for transit-unseal #221
Comments
will it be in the roadmap ? |
Hi @Ais8Ooz8, thanks for considering Bank-Vaults, also sorry for the late reply! You can specify a different place to store the root token and recovery keys for any Vault custom resource, in the
|
Answered by: #221 (comment) |
Preflight Checklist
Problem Description
We need a way to explicitly set the settings for the transit-unseal case — https://github.com/bank-vaults/vault-operator/blob/main/pkg/apis/vault/v1alpha1/vault_types.go
While there is an explicit way for the kv-unseal case — https://github.com/bank-vaults/vault-operator/blob/main/deploy/examples/cr-vault-kv-unseal.yaml
We see not very transparent recommendations on how to stop using Kubernetes Secrets — https://github.com/bank-vaults/vault-operator/blob/main/deploy/examples/cr-transit-unseal.yaml
Proposed Solution
We need a way to explicitly set the settings for the transit-unseal case — https://github.com/bank-vaults/vault-operator/blob/main/pkg/apis/vault/v1alpha1/vault_types.go
Alternatives Considered
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: