coulomb/railiance-enablement
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Declare Argo CD Core v3.5.3 on railiance01 and its resource bounds
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Has been cancelled
Details

Browse source 
Pinned core-install.yaml (sha256 1a87025d...c448) with a kustomize
resources patch for the four workloads. The unpatched pin diffs clean
against live; the resources patch is declared only, and its apply waits
on the founder in RAIL-EN-WP-0002-T02. SCOPE.md no longer says ArgoCD is
absent from 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:
tegwick 2026-09-21 18:41:24 +02:00
parent f91a5298cb
commit 70295b6b2b
8 changed files with 284 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

25
SCOPE.md
View file

@ -74,25 +74,26 @@ services. S5 applications consume S4 templates and conventions, while
## Current State
- Status: emerging, with reusable Forgejo workflow templates and an active
private-by-default template workplan.
- Status: emerging, with reusable Forgejo workflow templates and the
railiance01 ArgoCD declared state (RAIL-EN-WP-0002 active).
- S4 owns the consumer-facing contract for runner labels, registries,
credentials, and artifact evidence. `railiance-forge` continues to operate
those capabilities; they are not duplicated here.
- Implementation: ArgoCD is deployed in the `argocd` namespace on CoulombCore as
a cluster addon managed from S2 — verified still true 2026-08-12
- **But GitOps does not reach the live cluster.** ArgoCD is not deployed on
`railiance01`, its Applications target CoulombCore in-cluster, and no
`railiance01` namespace is ArgoCD-managed. The live workloads deploy by
Makefile, outside GitOps. Whether to adopt, retire or relocate ArgoCD is
reopened — see `railiance-platform/ArchitectureBlueprint.md` §5.6
- Stability: n/a for S4-owned content; ArgoCD itself runs, but two of its
Applications are Degraded and one is OutOfSync/Missing
- Implementation: Argo CD Core v3.5.3 (headless) is installed on
`railiance01` in namespace `argocd` since 2026-09-21. ArchitectureBlueprint
§5.6 (railiance-platform) is settled as **adopt properly**. Its declared
state is `deploy/argocd/railiance01/` (RAIL-EN-WP-0002). It has 0
Applications and 0 AppProjects, so no workload is under GitOps yet; the live
workloads still deploy by Makefile. Adoption (phase B) and retiring
CoulombCore's ArgoCD (phase C) each need a founder go-ahead
- Stability: the pinned install matches live (read-only server-side diff,
2026-09-21); resource requests/limits are declared but not yet applied, so
the pods are BestEffort until RAIL-EN-WP-0002-T02
- Usage: formal S4 tooling work begins after S3 baseline and should consume
runner/registry capabilities from `railiance-forge` until that migration
completes
- Honest gap: this layer's `INTENT.md` promises considerably more than the repo
contains (25 commits, no workplans). Read that as open debt, not description
contains. Read that as open debt, not description
---