Closed Ais8Ooz8 closed 2 months ago
will it be in the roadmap ? or you're still looking at some information with Hashicorp new's licence ?
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 vault-kv-unseal
example it is another Vault instance, the default is a Kubernetes secret, but you can (should) use another Vault, Azure, AWS, etc: https://github.com/bank-vaults/vault-operator/blob/b27d76f0f0ae2020c9a14eca0ae85ee13510a495/deploy/crd/bases/vault.banzaicloud.com_vaults.yaml#L1068
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