I’m currently faced with an issue of vaultAuthRef. I created the vault secrets operator in namespaceA and I want to create my VaultDynamicSecret resource in namespaceB. The installation of the Vault Secrets Operator is done fine and complete. however when I try to install the VaultDynamicSecret in a different namespace other than that of the vault secrets operator, the VaultAuthRef field doesn’t seem to fine the vaultAuth resource. it seems to be looking for it in the same namespace as VaultDynamicSecret. When I prefix it with the namespace, it now reads the namespace as a service account and now throws an error that it can’t find the service account.
This is how I install the VSO
helm upgrade --install --namespace external-secret vault-secrets-operator --values values.yaml hashicorp/vault-secrets-operator --version 0.3.1
apiVersion: secrets.hashicorp.com/v1beta1 kind: VaultDynamicSecret metadata: name: "vault-dynamic-secret-example" namespace: "my-test" spec: namespace: "vault/namespace/" vaultAuthRef: external-secret/default mount: "aws" path: "creds/aws-role-here" destination: name: "my-test-secret" create: true
kindly help me figure this out