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

Residual from STATE-WP-0091: pending pods in capacity evidence.
Some checks are pending
CI Smoke / host-smoke (push) Waiting to run
Details
CI Smoke / container-smoke (push) Waiting to run
Details

Browse source 
RCLUSTER-WP-0015 proposed. 105m remaining is not cluster admission.

Assistant: grok
Assistant-Session: 01a09dc1-b21e-77e1-919e-fcad2f82b267
This commit is contained in:
codex 2026-09-14 10:13:48 +02:00
parent db7860ec2e
commit faed07a0c9
1 changed files with 34 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

34
workplans/RCLUSTER-WP-0015-state-hub-surge-headroom.md Normal file
View file

@ -0,0 +1,34 @@
---
id: RCLUSTER-WP-0015
type: workplan
title: "Keep node remaining CPU honest for State Hub surge and pending demand"
domain: financials
repo: railiance-cluster
status: proposed
owner: codex
topic_slug: railiance
origin: residual
origin_ref: STATE-WP-0091
created: "2026-09-14"
updated: "2026-09-14"
related: [RCLUSTER-WP-0014, STATE-WP-0091, CUST-WP-0071]
---
Residual from STATE-WP-0091. State Hub now refuses promotion when remaining
CPU cannot cover its 100m API surge, and when unrelated pending pods would
eat the 5m sliver above 105m. Cluster observation must keep publishing
allocatable, allocated, **and pending-unrelated** demand. 105m remaining is
not capacity admission for factory or other zero-request workloads.
## Include pending pods in capacity observations
```task
id: RCLUSTER-WP-0015-T01
status: todo
priority: high
```
Extend `tools/observe_cluster_resources.py` / `make cluster-observe` so the
published observation names pending unscheduled pods and their requests.
State Hub's preflight already consumes that shape. Do not treat residual
millicores as a scheduling guarantee.