mirror of
https://github.com/ceph/ceph-csi.git
synced 2024-11-17 20:00:23 +00:00
f6894909d7
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> |
||
|---|---|---|
| .. | ||
| aws_metadata_test.go | ||
| aws_metadata.go | ||
| keyprotect_test.go | ||
| keyprotect.go | ||
| kms_test.go | ||
| kms.go | ||
| secretskms_test.go | ||
| secretskms.go | ||
| vault_sa_test.go | ||
| vault_sa.go | ||
| vault_test.go | ||
| vault_tokens_test.go | ||
| vault_tokens.go | ||
| vault.go | ||