Refresh Current State against the live clusters
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
parent
007df2b7b5
commit
a32a64454a
3 changed files with 104 additions and 2 deletions
19
SCOPE.md
19
SCOPE.md
|
|
@ -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`
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -16,6 +16,7 @@
|
|||
| workplan | RAIL-BS-WP-0011 | finished | — | workplans/RAIL-BS-WP-0011-legacy-meter-8h-capture-image-reconcile.md |
|
||||
| workplan | RAIL-BS-WP-0012 | finished | — | workplans/RAIL-BS-WP-0012-rail-kubernetes-extraction.md |
|
||||
| workplan | RAIL-BS-WP-0013 | finished | — | workplans/RAIL-BS-WP-0013-knative-substrate.md |
|
||||
| workplan | RAIL-BS-WP-0014 | ready | — | workplans/RAIL-BS-WP-0014-capacity-utilization-and-allocation-evidence.md |
|
||||
| task | RAIL-BS-ADHOC-2026-07-27-T01 | done | — | workplans/ADHOC-2026-07-27.md |
|
||||
| task | RAIL-BS-WP-0007-T01 | todo | — | workplans/RAIL-BS-WP-0007-threephoenix-ha-cluster.md |
|
||||
| task | RAIL-BS-WP-0007-T02 | todo | — | workplans/RAIL-BS-WP-0007-threephoenix-ha-cluster.md |
|
||||
|
|
@ -47,3 +48,6 @@
|
|||
| task | RAIL-BS-WP-0013-T02 | done | — | workplans/RAIL-BS-WP-0013-knative-substrate.md |
|
||||
| task | RAIL-BS-WP-0013-T03 | done | — | workplans/RAIL-BS-WP-0013-knative-substrate.md |
|
||||
| task | RAIL-BS-WP-0013-T04 | done | — | workplans/RAIL-BS-WP-0013-knative-substrate.md |
|
||||
| task | RAIL-BS-WP-0014-T01 | todo | — | workplans/RAIL-BS-WP-0014-capacity-utilization-and-allocation-evidence.md |
|
||||
| task | RAIL-BS-WP-0014-T02 | todo | — | workplans/RAIL-BS-WP-0014-capacity-utilization-and-allocation-evidence.md |
|
||||
| task | RAIL-BS-WP-0014-T03 | todo | — | workplans/RAIL-BS-WP-0014-capacity-utilization-and-allocation-evidence.md |
|
||||
|
|
|
|||
|
|
@ -0,0 +1,83 @@
|
|||
---
|
||||
id: RAIL-BS-WP-0014
|
||||
type: workplan
|
||||
title: "Publish cluster capacity, utilization, and allocation evidence"
|
||||
domain: financials
|
||||
repo: railiance-cluster
|
||||
status: ready
|
||||
owner: codex
|
||||
topic_slug: railiance
|
||||
created: "2026-08-11"
|
||||
updated: "2026-08-11"
|
||||
related:
|
||||
- RAIL-BS-WP-0007
|
||||
- RESOURCE-WP-0003
|
||||
state_hub_workstream_id: "ea6ec98a-0d65-4afa-b6c5-6e7ed34011ac"
|
||||
---
|
||||
|
||||
# RAIL-BS-WP-0014 — cluster resource evidence
|
||||
|
||||
## Goal
|
||||
|
||||
Publish reproducible non-secret evidence for
|
||||
`resource:railiance:reef-railiance:k3s`: capacity, requested and observed
|
||||
utilization, persistent-storage exposure, failure domains, and allocation
|
||||
drivers. Origin: `RESOURCE-WP-0003-T04` delegated evidence gap.
|
||||
|
||||
## T01 — Produce periodic cluster capacity observations
|
||||
|
||||
```task
|
||||
id: RAIL-BS-WP-0014-T01
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "a144bf1d-0402-4526-9bda-17846390270c"
|
||||
```
|
||||
|
||||
Collect node count, allocatable CPU/memory/storage/pods, workload requests and
|
||||
limits, observed usage when metrics are available, and PVC requested capacity.
|
||||
Aggregate by namespace/workload without exposing Secret data or pod
|
||||
environment. Preserve observation time, cluster identity, units, unavailable
|
||||
metrics, and source commands.
|
||||
|
||||
Done when repeated observations use a stable machine-readable interface and
|
||||
resource-control can distinguish headroom, reservations, and actual usage.
|
||||
|
||||
## T02 — Publish the failure-domain and storage contract
|
||||
|
||||
```task
|
||||
id: RAIL-BS-WP-0014-T02
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "6460d9aa-3ded-420a-bf01-f0ccdeee0a02"
|
||||
```
|
||||
|
||||
Expose the current node-to-host/provider failure-domain map and the actual
|
||||
storage-class/PVC durability contract. Link the target ThreePhoenix work in
|
||||
`RAIL-BS-WP-0007` without reporting target nodes or distributed storage as
|
||||
current capacity.
|
||||
|
||||
Done when consumers can calculate correlated-failure risk and recognize which
|
||||
state remains local to `railiance01`.
|
||||
|
||||
## T03 — Define technical allocation-driver evidence
|
||||
|
||||
```task
|
||||
id: RAIL-BS-WP-0014-T03
|
||||
status: todo
|
||||
priority: medium
|
||||
state_hub_task_id: "e5ff9b6c-e883-4356-9eca-b31757661d2f"
|
||||
```
|
||||
|
||||
Evaluate namespace/workload CPU-request hours, memory-request hours, PVC
|
||||
GB-month, and observed usage as allocation drivers. Publish numerator,
|
||||
denominator, residual/unallocated capacity, method version, and uncertainty;
|
||||
do not convert the result into booked spend.
|
||||
|
||||
Done when resource-control can create an explainable allocation and fin-hub can
|
||||
reconcile it to referenced financial facts.
|
||||
|
||||
## Acceptance
|
||||
|
||||
- [ ] Capacity evidence separates allocatable, requested, limited, and observed.
|
||||
- [ ] Current single-host/local-storage risk is machine-readable.
|
||||
- [ ] Allocation drivers reconcile to explicit totals and residuals.
|
||||
Loading…
Add table
Add a link
Reference in a new issue