Niels de Vos b866bd491c util: add vaultAuthNamespace option for Vault KMS ... The new `vaultAuthNamespace` configuration parameter can be set to the Vault Namespace where the authentication is setup in the service. Some Hashicorp Vault deployments use sub-namespaces for their users/tenants, with a 'root' namespace where the authentication is configured. This requires passing of different Vault namespaces for different operations. Example: - the Kubernetes Auth mechanism is configured for in the Vault Namespace called 'devops' - a user/tenant has a sub-namespace called 'devops/website' where the encryption passphrases can be placed in the key-value store The configuration for this, then looks like: vaultAuthNamespace: devops vaultNamespace: devops/homepage Note that Vault Namespaces are a feature of the Hashicorp Vault Enterprise product, and not part of the Open Source version. This prevents adding e2e tests that validate the Vault Namespace configuration. Signed-off-by: Niels de Vos <ndevos@redhat.com> (cherry picked from commit f2d5c2e0df)		2021-08-05 06:44:23 +00:00
..
cephfs	cleanup: modifies the error caused due to merged PRs	2021-07-22 18:15:48 +00:00
controller	cleanup: resolve nlreturn linter issues	2021-07-22 06:05:01 +00:00
csi-common	cleanup: resolve nlreturn linter issues	2021-07-22 06:05:01 +00:00
journal	cleanup: resolve nlreturn linter issues	2021-07-22 06:05:01 +00:00
liveness	cleanup: resolve nlreturn linter issues	2021-07-22 06:05:01 +00:00
rbd	rbd: use rados namespace for manager command	2021-07-28 03:48:33 +00:00
util	util: add vaultAuthNamespace option for Vault KMS	2021-08-05 06:44:23 +00:00