Niels de Vos 82557e3f34 util: allow configuring VAULT_BACKEND for Vault connection ...

It seems that the version of the key/value engine can not always be
detected for Hashicorp Vault. In certain cases, it is required to
configure the `VAULT_BACKEND` (or `vaultBackend`) option so that a
successful connection to the service can be made.

The `kv-v2` is the current default for development deployments of
Hashicorp Vault (what we use for automated testing). Production
deployments default to version 1 for now.

Signed-off-by: Niels de Vos <ndevos@redhat.com>

2021-07-22 13:02:47 +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

doc: add example for Tenant ServiceAccount

2021-07-13 17:16:35 +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: allow configuring VAULT_BACKEND for Vault connection

2021-07-22 13:02:47 +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