coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Record that ArgoCD is not on railiance01 (read-only check, 2026-09-21).
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 4s
Details

Browse source 
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
codex 2026-09-21 15:48:29 +02:00
parent e98dd26153
commit 28bd1be8ec
1 changed files with 14 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/kubernetes-change-gate-decision.md
View file

@ -61,7 +61,20 @@ ops-mason's executor is narrower than a generic `kubectl apply`:
This decision relies on those limits. Widening them is a new decision.
## Not verified here, and possibly not true
## Verified 2026-09-21: ArgoCD is not on railiance01
A read-only check, run by the custodian over SSH with the founder's approval, established:
- The node is `92.205.62.239`, the single k3s control-plane node.
- The `argocd` namespace does not exist.
- The `applications.argoproj.io` CRD does not exist.
- The resource type `applications` is unknown to the API server.
Only `get` was used; nothing was applied, patched or synced.
**So the production row has no working path on railiance01.** Until one exists, the transition rule applies to every production-tier target there. Installing ArgoCD on railiance01 is a cluster-layer change and needs its own founder go-ahead. It is not part of this decision.
### What the records said before the check
Whether ArgoCD runs on railiance01 at all is unverified, and railiance-platform's own records point the other way: