ceph-csi/examples/kms/vault
Niels de Vos f584db41e6 util: add vaultDestroyKeys option to destroy Vault kv-v2 secrets
Hashicorp Vault does not completely remove the secrets in a kv-v2
backend when the keys are deleted. The metadata of the keys will be
kept, and it is possible to recover the contents of the keys afterwards.

With the new `vaultDestroyKeys` configuration parameter, this behaviour
can now be selected. By default the parameter will be set to `true`,
indicating that the keys and contents should completely be destroyed.
Setting it to any other value will make it possible to recover the
deleted keys.

Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-08-06 12:19:18 +00:00
..
aws-credentials.yaml doc: add configuration example for Amazon KMS 2021-04-06 07:33:54 +00:00
csi-kms-connection-details.yaml util: add vaultDestroyKeys option to destroy Vault kv-v2 secrets 2021-08-06 12:19:18 +00:00
csi-vaulttokenreview-rbac.yaml Adds per volume encryption with Vault integration 2020-02-05 05:18:56 +00:00
kms-config.yaml util: add vaultDestroyKeys option to destroy Vault kv-v2 secrets 2021-08-06 12:19:18 +00:00
tenant-config.yaml util: allow configuring VAULT_BACKEND for Vault connection 2021-07-22 13:02:47 +00:00
tenant-sa-admin.yaml util: allow configuring VAULT_BACKEND for Vault connection 2021-07-22 13:02:47 +00:00
tenant-sa.yaml util: allow configuring VAULT_BACKEND for Vault connection 2021-07-22 13:02:47 +00:00
tenant-token.yaml e2e: add test for VaultTokensKMS support 2020-12-14 14:45:09 +00:00
user-secret.yaml e2e: add e2e for user secret based metadata encryption 2021-07-08 17:06:02 +00:00
vault-psp.yaml Adds per volume encryption with Vault integration 2020-02-05 05:18:56 +00:00
vault.yaml e2e: add securityContext.runAsUser to vault-init-job 2021-07-13 17:16:35 +00:00