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

Refresh Current State against the live clusters
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Verified against railiance01 on 2026-08-12 once API access was restored.

Corrections: two clusters are managed, not one - railiance01 is the current
primary running the live workloads, CoulombCore is the older frozen cluster.
Traefik is the ingress controller, not nginx. ArgoCD is not on railiance01 at
all; it runs on CoulombCore only, so the previous entry was accurate for that
host but misleading as a general cluster-level claim.

Adds the verified addon and CNPG cluster inventory, notes the absence of any
monitoring stack, and points at RAIL-HO-WP-0009 for the source-restricted k3s
API.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
codex 2026-08-12 00:04:23 +02:00
parent 007df2b7b5
commit a32a64454a
3 changed files with 104 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

19
SCOPE.md
View file

@ -75,8 +75,23 @@ future `rail-kubernetes` repo and must not be treated as long-term S2 scope.
- Status: active / stable
- Implementation: k3s baseline, age-encrypted backup, kubeconfig delivery, and cluster operator/addon management are established; generic workload lifecycle docs/tooling remain here as transition debt pending `rail-kubernetes` extraction
- Open work: RAIL-BS-WP-0007 ThreePhoenix HA cluster (active, 0/7); RAIL-BS-WP-0008 activity-core WP-0016 deploy (ready); RAIL-BS-WP-0009 admin-sync smoke (ready); RAIL-BS-WP-0012 rail-kubernetes extraction (active)
- Usage: core Kubernetes runtime for all Railiance deployments; runs on COULOMBCORE (92.205.130.254)
- Also deployed at cluster level: cert-manager, ArgoCD, CloudNative PG operator (cnpg), nginx ingress, SSO stack (mfa + sso namespaces via net-kingdom)
- Usage: core Kubernetes runtime for all Railiance deployments. **Two clusters
are managed**: `railiance01` (92.205.62.239) is the current primary and runs
the live workloads; `CoulombCore` (92.205.130.254) is the older cluster and is
under a production freeze
- Verified on `railiance01` 2026-08-12 (k3s v1.35.1+k3s1, node Ready):
cert-manager, CloudNative PG operator (cnpg), **Traefik** ingress (k3s
default, in `kube-system`), Kourier + Knative Serving, External Secrets,
OpenBao, SSO stack (`mfa` + `sso` via net-kingdom)
- **Not** on `railiance01`: ArgoCD (it runs on CoulombCore only) and nginx
ingress (Traefik is the controller). Earlier revisions of this file listed
both — the ArgoCD entry was accurate for CoulombCore, the nginx entry was not
- CNPG clusters on `railiance01`: `apps-pg`, `forgejo-db`, `net-kingdom-pg`,
`platform-pg`, `state-hub-db`, `target-revenue-pg`, `user-engine-pg`
- No monitoring stack is deployed on either cluster — observability is Q2 and
homed in `railiance-telemetry`, which is seeded but not implemented
- k3s API access is source-restricted by UFW; see `railiance-infra`
`RAIL-HO-WP-0009`
---