Niels de Vos f6894909d7 util: use vaultNamespace if vaultAuthNamespace is not set ... When a tenant configures `vaultNamespace` in their own ConfigMap, it is not applied to the Vault configuration, unless `vaultAuthNamespace` is set as well. This is unexpected, as the `vaultAuthNamespace` usually is something configured globally, and not per tenant. The `vaultAuthNamespace` is an advanced option, that is often not needed to be configured. Only when tenants have to configure their own `vaultNamespace`, it is possible that they need to use a different `vaultAuthNamespace`. The default for the `vaultAuthNamespace` is now the `vaultNamespace` value from the global configuration. Tenants can still set it to something else in their own ConfigMap if needed. Note that Hashicorp Vault Namespaces are only functional in the Enterprise version of the product. Therefor this can not be tested in the Ceph-CSI e2e with the Open Source version of Vault. Fixes: https://bugzilla.redhat.com/2050056 Reported-by: Rachael George <rgeorge@redhat.com> Signed-off-by: Niels de Vos <ndevos@redhat.com>		2022-02-07 08:20:48 +00:00
..
cephfs	cephfs: fix error logging in filesystem.go	2022-01-27 14:31:12 +00:00
controller	rbd: remove retrieving volumeHandle from PV annotation	2021-12-17 03:38:29 +00:00
csi-addons	rbd: add NetworkFence operation	2022-01-07 14:48:12 +00:00
csi-common	rbd: introduce a helper function to detect multi writer,block & rwofile	2022-01-11 19:40:22 +00:00
journal	cleanup: remove unwanted type declaration	2022-01-24 05:25:11 +00:00
kms	util: use vaultNamespace if vaultAuthNamespace is not set	2022-02-07 08:20:48 +00:00
liveness	cleanup: move log functions to new internal/util/log package	2021-08-26 09:34:05 +00:00
rbd	cleanup: remove thick provisioning code	2022-01-28 11:17:15 +00:00
util	cleanup: remove ceph.conf WA options which are already fixed	2022-02-04 15:42:32 +00:00