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
This commit is contained in:
parent
2d79c2e4e5
commit
6e399bbe64
6 changed files with 347 additions and 25 deletions
16
openbao/eso-auth-recovery/rpf-wp-0045-serviceaccounts.yaml
Normal file
16
openbao/eso-auth-recovery/rpf-wp-0045-serviceaccounts.yaml
Normal file
|
|
@ -0,0 +1,16 @@
|
|||
# RPF-WP-0045: dedicated ESO identities for the two stores still on static
|
||||
# tokens. Not applied by the RPF-WP-0037 helper (it reads serviceaccounts.yaml).
|
||||
# Apply only in RPF-WP-0045-T03, after the founder's go-ahead.
|
||||
apiVersion: v1
|
||||
kind: ServiceAccount
|
||||
metadata:
|
||||
name: activity-core-eso
|
||||
namespace: activity-core
|
||||
automountServiceAccountToken: false
|
||||
---
|
||||
apiVersion: v1
|
||||
kind: ServiceAccount
|
||||
metadata:
|
||||
name: email-connect-eso
|
||||
namespace: email-connect
|
||||
automountServiceAccountToken: false
|
||||
Loading…
Add table
Add a link
Reference in a new issue