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

Close Knative CPU request handoff with installer evidence

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e396-d089-7653-b0a1-734cac532913
This commit is contained in:
tegwick 2026-09-27 18:01:25 +02:00
parent 8caf491854
commit cd38dba365
4 changed files with 43 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/substrate-runbook.md
View file

@ -22,10 +22,16 @@ upstream's. These values were set live on 2026-09-21 as
because the node had 100% of its allocatable CPU requested and backups could
not be scheduled. Record: `the-custodian/docs/kubernetes-change-gate-decision.md`.
A plain re-apply or upgrade of the upstream manifests restores the upstream
column. Every apply or upgrade must apply these patches afterwards, and an
upgrade to a new version needs a new `substrate/<version>/` with container
names re-checked against that release.
The owner installer now renders these requests into the manifests before apply,
using separate Serving and Kourier overlays. Its verifier checks all six values.
Implementation and read-only live diff evidence are recorded in
[RAIL-BS-WP-0015](../../railiance-cluster/workplans/RAIL-BS-WP-0015-knative-declared-cpu-requests.md),
implemented by railiance-cluster commit `3a5432270e275e978d6c8a99529fa7f8be6eef57`.
A plain re-apply of unpatched upstream manifests restores the upstream column.
Every apply or upgrade must preserve these patches, and an upgrade to a new
version needs a new `substrate/<version>/` with container names re-checked
against that release.
## Lessons