Record pilot CPU reservation constraint before placement
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc
This commit is contained in:
parent
6988111303
commit
f390c9f91d
3 changed files with 35 additions and 1 deletions
|
|
@ -8,5 +8,22 @@
|
|||
"live_mutations": 0,
|
||||
"customer_data_read": false,
|
||||
"credentials_read": false,
|
||||
"claim": "Historical runbook does not establish current deployment; no data-loss conclusion."
|
||||
"claim": "Historical runbook does not establish current deployment; no data-loss conclusion.",
|
||||
"capacity_observed_at": "2026-09-11T14:49:11.718210+00:00",
|
||||
"placement_capacity": {
|
||||
"node_allocatable_cpu_m": 4000,
|
||||
"allocated_cpu_requests_m": 3905,
|
||||
"unreserved_cpu_m": 95,
|
||||
"pilot_cpu_request_m": 100,
|
||||
"fits_current_cpu_reservations": false,
|
||||
"measurement": "kubectl describe nodes allocated requests; not actual CPU utilization"
|
||||
},
|
||||
"shared_application_database": {
|
||||
"namespace": "databases",
|
||||
"cluster": "apps-pg",
|
||||
"instances": 1,
|
||||
"ready": 1,
|
||||
"phase": "Cluster in healthy state",
|
||||
"vergabe_database_or_role_presence_checked": false
|
||||
}
|
||||
}
|
||||
|
|
|
|||
|
|
@ -106,3 +106,11 @@ The published image contains the invited login/private-download gate. Exact
|
|||
company/host/data binding, native deployment, coherent restore and two-user
|
||||
acceptance remain open. See `docs/evidence/2026-09-11-invited-pilot-release.json`
|
||||
for source, CI and artifact receipts; this candidate has not been deployed.
|
||||
|
||||
|
||||
The shared `databases/apps-pg` cluster is currently healthy (1/1). The node has
|
||||
4000m allocatable CPU and 3905m in requests, leaving 95m against this pilot's
|
||||
100m request. This is a reservation constraint, not a utilization measurement.
|
||||
RAPPS-WP-0014-T02 retains capacity admission before deployment; use existing
|
||||
owner observations or add capacity, and retain operating room for factory
|
||||
services. Do not silently reduce the pilot request to make the chart fit.
|
||||
|
|
|
|||
|
|
@ -48,6 +48,15 @@ data. Resolve target inventory before using historical runbook names: the
|
|||
checked Railiance cluster has no vergabe-teilnahme namespace or matching
|
||||
Deployment on 2026-09-11. Do not infer data loss or authorization to recreate it.
|
||||
|
||||
Current metadata also shows `databases/apps-pg` healthy (1/1), but the sole node
|
||||
has 3905m CPU requests against 4000m allocatable: only 95m remains versus the
|
||||
pilot's 100m request. Placement does not currently fit. Resolve capacity with
|
||||
the Railiance owner using measured demand or added capacity, and reserve room
|
||||
for the remaining factory services/operations; do not lower requests merely
|
||||
to pass scheduling. STATE-WP-0091 is the existing shared-headroom observation
|
||||
return, not a grant to resize unrelated workloads. Database/role/data presence
|
||||
has not been read. See the dated inventory receipt.
|
||||
|
||||
Use `docs/vergabe-teilnahme-pilot.md` for the review packet. Secret creation,
|
||||
operator access and placement consume existing platform lanes; they do not
|
||||
create a parallel identity framework. The public edge needs an admitted login
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue