From 28bd1be8ec18b6cb6d32d2d723c173c4e1d0ce28 Mon Sep 17 00:00:00 2001 From: codex Date: Mon, 21 Sep 2026 15:48:29 +0200 Subject: [PATCH] Record that ArgoCD is not on railiance01 (read-only check, 2026-09-21). Co-Authored-By: Claude Opus 5 --- docs/kubernetes-change-gate-decision.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/docs/kubernetes-change-gate-decision.md b/docs/kubernetes-change-gate-decision.md index 9a3a9a8..a182298 100644 --- a/docs/kubernetes-change-gate-decision.md +++ b/docs/kubernetes-change-gate-decision.md @@ -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: