railiance-platform/argocd/platform-addons/openbao-secretstore/openbao-email-connect.clustersecretstore.yaml
codex 6e399bbe64
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 6s
RPF-WP-0045: plan Kubernetes-auth migration for openbao-activity-core and openbao-email-connect
Declares target store specs, two exact-path policies and two ESO
ServiceAccounts. Nothing applied; live steps wait on the founder.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
2026-09-21 19:18:59 +02:00

30 lines
984 B
YAML

# RPF-WP-0045: exact namespace/SA/audience Kubernetes auth; no static token.
# DECLARED TARGET, NOT YET LIVE. Live still references the expired
# external-secrets/openbao-email-connect-eso-token until RPF-WP-0045-T03.
# Nothing syncs this file (excluded from the kustomization). CCR: CCR-2026-0010.
apiVersion: external-secrets.io/v1beta1
kind: ClusterSecretStore
metadata:
name: openbao-email-connect
labels:
app.kubernetes.io/part-of: railiance-gitops
railiance-platform/component: external-secrets
app.kubernetes.io/name: email-connect
spec:
provider:
vault:
server: http://openbao.openbao.svc:8200
path: platform
version: v2
auth:
kubernetes:
mountPath: kubernetes
role: email-connect-transactional-eso
serviceAccountRef:
name: email-connect-eso
namespace: email-connect
audiences:
- openbao
conditions:
- namespaces:
- email-connect