Decide blueprint 5.6 (adopt ArgoCD) and plan phase B adoption on railiance01.
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 6s

Records the founder's 2026-09-21 decision, read-only diff evidence for the
four Applications, and RPF-WP-0044 (one founder go-ahead per app). Nothing
applied.

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:
codex 2026-09-21 18:44:51 +02:00
parent 0b70765e0a
commit f1e885aa9e
4 changed files with 398 additions and 24 deletions

View file

@ -332,7 +332,27 @@ to `railiance-master` (`04c776c4`, amended `f88f938d`).
- delete the local `~/railiance-bootstrap` directory, which is a mis-cloned copy
of `railiance-cluster.git`
### 5.6 Does Railiance use ArgoCD? → **REOPENED 2026-08-12 on corrected evidence**
### 5.6 Does Railiance use ArgoCD? → **DECIDED 2026-09-21: option 1, adopt properly**
**Decision.** Bernd Worsch, the founder, decided on 2026-09-21, exercising
`GOVERN @ estate`, for option 1 below: **adopt properly**. ArgoCD runs on
railiance01, and the live workloads are brought under GitOps one application
at a time. Record: `the-custodian/docs/kubernetes-change-gate-decision.md`
§ "ArgoCD installed on railiance01 (phase A)".
- **Phase A, done 2026-09-21:** upstream Argo CD Core v3.5.3 (headless)
installed in namespace `argocd` on railiance01 by the custodian session,
`ADMINISTER @ realm:kubernetes/railiance01`, `activation=APPROVED`. 0
Applications, 0 AppProjects, nothing adopted. The install is not yet
declared in any repository.
- **Phase B, planned, not started:** adopt external-secrets,
openbao-secretstore, issue-core and target-revenue, each with its own
founder go-ahead. Plan and read-only diff evidence: `RPF-WP-0044`,
`docs/evidence/argocd-phase-b-adoption-diff-2026-09-21.json`.
- **Phase C, not planned yet:** retire coulombcore's ArgoCD.
The evidence that reopened the question on 2026-08-12 follows unchanged.
Decided 2026-08-11 as "keep it", on the basis that S3 runs ArgoCD as its live
deployment mechanism. **That basis was wrong.** Verified against both clusters