Record the ArgoCD lane as the production change path and plan policy-nexus onboarding.
Founder decision 2026-09-21 (the-custodian/docs/kubernetes-change-gate-decision.md). RPF-WP-0043 plans, and does not perform, the policy-nexus adoption; it waits on the founder's go-ahead. Records that this repository cannot show ArgoCD reconciling on railiance01. 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
ad88639a53
commit
adb5a7249c
4 changed files with 285 additions and 0 deletions
|
|
@ -13,6 +13,13 @@ tenant workloads is:
|
|||
k8s/railiance/
|
||||
```
|
||||
|
||||
Since the founder's decision of 2026-09-21, this directory is the change path
|
||||
for `production-approved` workloads (see `docs/argocd-gitops.md` § Production
|
||||
Change Path). A merge here is a live production change. Adopting a workload
|
||||
that is already running (for example `rapp-policy-nexus`, RPF-WP-0043) needs the
|
||||
founder's go-ahead and a diff first. Do not add an Application for a
|
||||
running workload directly.
|
||||
|
||||
Do not commit Kubernetes Secret values, ArgoCD repository credentials, OpenBao
|
||||
tokens, deploy keys, or API keys here.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue