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

Publish pending unscheduled pods in cluster observations.
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
RAIL-BS-WP-0014: residual millicores count scheduled pods only.
state_hub_preflight_observation matches the STATE-WP-0091 fixture shape.

Assistant: grok
Assistant-Session: 01a09dc1-b21e-77e1-919e-fcad2f82b267
This commit is contained in:
codex 2026-09-14 10:34:27 +02:00
parent 551a898e4d
commit b36ac28b49
4 changed files with 121 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/cluster-resource-evidence.md
View file

@ -6,7 +6,11 @@ requests, limits, optional observed usage, PVC demand, storage-class behavior,
and measurement gaps. It never reads Secret objects or pod environments.
The allocation section publishes raw numerators, denominators, residual
capacity, and `cluster-raw-drivers-v1`. It does not select a financial
capacity, and `cluster-raw-drivers-v1`. Residual millicores exclude
pending unscheduled pods; those pods are listed under
`allocation.pending_unscheduled` and projected as
`state_hub_preflight_observation` for STATE-WP-0091. Residual capacity is
**not** a kube-scheduler guarantee. It does not select a financial
allocation formula or write booked cost; those decisions remain with
resource-control.