Files
devops-infra-argo-config-gcp/secretstores/jenkins-admin-credentials.yaml
T
Mukul SharmaandClaude Opus 5 3b11f3e0ea Point comments at paths that still exist after the homelab overrides were removed
References to helm-overrides/k8s-admin-prd-ase1 now either name the
homelab repo that still has that folder, or point at the GKE equivalent
under gke-toolshed-prd-usc1. Comments only; no rendered values change.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fn2kUxyYNY4ApytbLiGWeY
2026-09-17 18:02:04 +05:30

27 lines
832 B
YAML

# Unlike gitea-admin-credentials, this one's Vault-backed from day one —
# no manual kubectl-created Secret ever existed for Jenkins. Keys match
# what the chart's controller.admin.userKey/passwordKey expect — see
# devops-infra-helm-charts-gcp/helm-overrides/gke-toolshed-prd-usc1/jenkins/custom-values.yaml.
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: jenkins-admin-credentials
namespace: jenkins
spec:
refreshInterval: 1h
secretStoreRef:
name: vault-backend
kind: ClusterSecretStore
target:
name: jenkins-admin-credentials
creationPolicy: Owner
data:
- secretKey: jenkins-admin-user
remoteRef:
key: jenkins/admin
property: username
- secretKey: jenkins-admin-password
remoteRef:
key: jenkins/admin
property: password