You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to utilize your secret manager to use in our kubernetes cluster, but we have faced a trouble: the custom resource definition in secret manager reuqires to map keys from Vault's secret object to kubernetes secret object.
We need to sync the secrets from Vault to kubernetes when user updates the Vault secret manually, without need to commit any configuration changes in repository.
Is it possible to create 1-to-1 mapping from Vault secret object to kubernetes secret object with your tool?
The text was updated successfully, but these errors were encountered:
Hi @s-vitaliy can you put an example on what you are trying to achieve? If I understood correctly, what you'd like is not having to specify the keys in the vault path at all, so secrets-manager will actually pull the keys and create a k8s secret with the same key names? Is that what you're suggesting?
Hi,
We would like to utilize your secret manager to use in our kubernetes cluster, but we have faced a trouble: the custom resource definition in secret manager reuqires to map keys from Vault's secret object to kubernetes secret object.
We need to sync the secrets from Vault to kubernetes when user updates the Vault secret manually, without need to commit any configuration changes in repository.
Is it possible to create 1-to-1 mapping from Vault secret object to kubernetes secret object with your tool?
The text was updated successfully, but these errors were encountered: