updated to hopefully correct authentication

This commit is contained in:
TapTap committed 2026-10-17 12:41:47 +02:00
1 parent ad7c827f26
commit 6b4422399b
1 file changed
+22 -12
+22 -12
View File
@@ -4,18 +4,28 @@ metadata:
name: vault-backend name: vault-backend
spec: spec:
provider: provider:
kubernetes:
server:
url: "http://default.svc.cluster.local"
vault: vault:
server: "http://vault.hashicorp-vault.svc.cluster.local:8200" server: "http://vault.hashicorp-vault.svc.cluster.local:8200"
path: "secret" path: "secret"
# Version is the Vault KV secret engine version. version: "v2"
# This can be either "v1" or "v2", defaults to "v2" auth:
# version: "v2" # Authenticate against Vault using a Kubernetes ServiceAccount
# auth: # token stored in a Secret.
# # points to a secret that contains a vault token # https://www.vaultproject.io/docs/auth/kubernetes
# # https://www.vaultproject.io/docs/auth/token kubernetes:
# tokenSecretRef: # Path where the Kubernetes authentication backend is mounted in Vault
# name: "vault-token" mountPath: "kubernetes"
# key: "token" # A required field containing the Vault Role to assume.
role: "eso-store-role"
# Optional service account field containing the name
# of a kubernetes ServiceAccount
serviceAccountRef:
name: "eso-vault-sa"
namespace: external-secrets
audiences:
- vault
# # Optional secret field containing a Kubernetes ServiceAccount JWT
# # used for authenticating with Vault
# secretRef:
# name: "my-secret"
# key: "vault"