-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Weird error in when configuring Vault provider #1024
Copy link
Copy link
Closed
Labels
StaleThis issue/Pull Request is stale and will be automatically closedThis issue/Pull Request is stale and will be automatically closedarea/vaultIndicates an issue or PR related to Vault.Indicates an issue or PR related to Vault.kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Description
I have the following secretStore config:
apiVersion: external-secrets.io/v1beta1
kind: SecretStore
metadata:
labels:
app.kubernetes.io/instance: dev-operators-secretstore
name: vault-secret-store
namespace: dev-operators
spec:
provider:
vault:
auth:
kubernetes:
mountPath: kubernetes
role: dev-operators
serviceAccountRef:
name: secret-store
caProvider:
key: ca-bundle.crt
name: vault-ca-bundle
type: ConfigMap
path: dev-operators
server: 'https://myvault:8200'
version: v2
However, This results in the following error in the events of the resource:
cannot set Vault CA certificate: an empty namespace may not be set when a resource name is provided
I'm at a total loss here... Not only are Vault namespaces an enterprise feature, so I don't see why I should specify it since I'm on the OSS version, but I totally don't understand what it has to do with the certficate config.
And yes, I verified the referenced configmap exists, same for the service account.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
StaleThis issue/Pull Request is stale and will be automatically closedThis issue/Pull Request is stale and will be automatically closedarea/vaultIndicates an issue or PR related to Vault.Indicates an issue or PR related to Vault.kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Type
Projects
Status
Done