unboundsoftware/schemas
6
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases 33 Activity

fix(k8s): raise schemas CPU request from 20m to 100m #840

Merged
argoyle merged 1 commits from bump-schemas-cpu-request into main 2026-05-19 07:23:06 +00:00
Conversation 0 Commits 1 Files Changed 1
+1 -1

1 Commits

Author SHA1 Message Date
argoyle dae4e8a135 fix(k8s): raise schemas CPU request from 20m to 100m
schemas / vulnerabilities (pull_request) Successful in 2m7s
Details
schemas / check (pull_request) Successful in 2m52s
Details
schemas / check-release (pull_request) Successful in 5m32s
Details
pre-commit / pre-commit (pull_request) Successful in 7m2s
Details
schemas / build (pull_request) Successful in 6m24s
Details
schemas / deploy-prod (pull_request) Has been skipped
Details 
HPA was pinning the deployment at maxReplicas (4) even though aggregate
CPU usage was low. The service is event-driven: pods sit at ~0-1m idle
but spike to 100-300m per supergraph query. With requests.cpu=20m those
bursts read as 500-1500% utilization, so the HPA's 60% target was
constantly exceeded on whichever pod handled the request.

Raise the request to 100m so bursts read as 100-300% instead. Combined
with the HPA's downscale stabilization window this lets replicas settle
back to minReplicas (2) between bursts.
 2026-05-19 09:07:39 +02:00