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

Restore State Hub's CPU request to the chart's 250m on railiance01.
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
The 100m override worked around a node with <250m unallocated. Knative and
Kourier released ~830m of requests on 2026-09-21, and State Hub bursts past
400m under concurrent agent load while reserving only 100m.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
This commit is contained in:
tegwick 2026-09-21 18:36:31 +02:00
parent b434deafc7
commit 6b97d01861
1 changed files with 5 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

8
deploy/railiance/apps/helm/state-hub-values.yaml
View file

@ -35,10 +35,12 @@ config:
sbomNexusWriteMode: nexus
resources:
# The single 4-core node currently has less than 250m unallocated. Keep enough
# headroom for maxSurge=1 so State Hub can roll without an outage.
# Restored to the chart's 250m on 2026-09-21. The earlier 100m was a workaround
# for a node with <250m unallocated; ~830m of Knative/Kourier requests were
# released that day (the-custodian docs/kubernetes-change-gate-decision.md).
# State Hub idles near 5m but bursts past 400m under concurrent agent load.
requests:
cpu: 100m
cpu: 250m
memory: 512Mi
limits:
cpu: 1000m