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

chore: align ThreePhoenix and capacity workplans with current axes
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Cite ADR-0006/0008, cancel leaked PG/forge tasks, retitle ingress to
Traefik, and fix the RAIL-BS-WP- convention in AGENTS.md.
This commit is contained in:
codex 2026-08-15 20:52:03 +02:00
parent 2838d620d7
commit 452e1d7f7f
4 changed files with 78 additions and 59 deletions
Download patch file Download diff file Expand all files Collapse all files

2
SCOPE.md
View file

@ -74,7 +74,7 @@ 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)
- Open work: RAIL-BS-WP-0007 ThreePhoenix HA cluster (backlog); RAIL-BS-WP-0014 cluster capacity evidence (ready)
- 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