RAIL-KNATIVE-WP-0003: applied on railiance01, finished

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 276069@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c
This commit is contained in:
tegwick 2026-10-21 21:07:29 +02:00
parent 894530a9b6
commit affe67a4bc

View file

@ -4,7 +4,7 @@ type: workplan
title: "Cap Knative HPA ceilings for one node and trim substrate CPU requests to 60m" title: "Cap Knative HPA ceilings for one node and trim substrate CPU requests to 60m"
domain: financials domain: financials
repo: rail-knative repo: rail-knative
status: active status: finished
owner: codex owner: codex
topic_slug: railiance topic_slug: railiance
created: "2026-10-21" created: "2026-10-21"
@ -80,10 +80,8 @@ and three HPA `maxReplicas`; memory, limits and `minReplicas` unchanged.
```task ```task
id: RAIL-KNATIVE-WP-0003-T02 id: RAIL-KNATIVE-WP-0003-T02
status: wait status: done
priority: high priority: high
needs_human: true
blocking_reason: "Coordinator applies wave-1 changes one owner at a time after review; railiance-cluster overlays must follow this declaration"
state_hub_task_id: "1e205e27-1c3a-5a16-a787-0afb3b35f75a" state_hub_task_id: "1e205e27-1c3a-5a16-a787-0afb3b35f75a"
``` ```
@ -169,3 +167,14 @@ Risks: a 10m request gives these pods little CPU weight under node contention
and gateway to 3 pods, which on one node is the practical ceiling anyway; the and gateway to 3 pods, which on one node is the practical ceiling anyway; the
80% PDBs on activator, webhook and gateway already allow 0 disruptions at 1 80% PDBs on activator, webhook and gateway already allow 0 disruptions at 1
replica (unchanged, but it blocks node drain). replica (unchanged, but it blocks node drain).
## Applied — 2026-10-21
Applied with the workstation kubeconfig under the founder's wave-1 authorization (the-custodian docs/decisions/2026-10-21-cust-wp-0071-delivery-interview.md), using the output of the railiance-cluster renderer at 3b18b84.
- HPA max is now 3/2/3, min 1.
- All six deployments request 10m CPU and are Ready 1/1.
- Kourier is still ClusterIP, and the rapp-qonto Knative service is Ready.
- Node CPU requests fell from 3605m to 3445m (−160m), as planned.
The cluster policy `reject-secret-last-applied` refused the Knative webhook certificate object in the render. Knative generates its contents at runtime, so it stayed unchanged; the fix is RCLUSTER-WP-0020-T04. Evidence: the-custodian docs/evidence/2026-10-21-wave1-apply.md.