railiance-platform/docs/provisioning-windows/2026-10-04-1000/keycape/eso.draft.yaml
codex 26dd803410 Place the ESO audience under serviceAccountRef (ESO v1 schema)
The server dry run rejected spec.provider.vault.auth.kubernetes.audiences. The
same audience, openbao, now sits under serviceAccountRef, as in openbao-reuse.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 132360@bnt-lap001
Assistant-Session: 769b1afd-4330-4c86-96b2-e510e26db42b
2026-10-07 02:05:53 +02:00

54 lines
1.5 KiB
YAML

# Admission approved by founder decision 2ab717e1-7881-491e-aed4-28946550c289 (A2). Apply only under the separate step-2 go, after the custody run.
apiVersion: external-secrets.io/v1
kind: ClusterSecretStore
metadata:
name: openbao-keycape-secrets-engine-openbao
annotations:
railiance.io/credential-change: CCR-2026-0033
railiance.io/admission: approved
spec:
provider:
vault:
server: http://openbao.openbao.svc:8200
path: platform
version: v2
auth:
kubernetes:
mountPath: kubernetes
role: external-secrets-keycape-secrets-engine-openbao
serviceAccountRef:
name: external-secrets
namespace: external-secrets
audiences:
- openbao
conditions:
- namespaces:
- sso
---
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: keycape-secrets-engine-openbao-client
namespace: sso
annotations:
railiance.io/credential-change: CCR-2026-0033
railiance.io/admission: approved
spec:
refreshInterval: 5m
secretStoreRef:
kind: ClusterSecretStore
name: openbao-keycape-secrets-engine-openbao
target:
name: keycape-secrets-engine-openbao-client
creationPolicy: Owner
deletionPolicy: Retain
template:
metadata:
annotations:
railiance.io/credential-change: CCR-2026-0033
railiance.io/admission: approved
data:
- secretKey: client-secret
remoteRef:
key: workloads/keycape/secrets-engine-openbao
property: CLIENT_SECRET