# 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/helm-overrides/k8s-admin-prd-ase1/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