From dae4e8a135206d8fe7e2e7ff0fbc3447482ccdf8 Mon Sep 17 00:00:00 2001 From: Joakim Olsson Date: Tue, 19 May 2026 09:07:39 +0200 Subject: [PATCH] fix(k8s): raise schemas CPU request from 20m to 100m 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. --- k8s/deploy.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/k8s/deploy.yaml b/k8s/deploy.yaml index 0f051cf..2981097 100644 --- a/k8s/deploy.yaml +++ b/k8s/deploy.yaml @@ -42,7 +42,7 @@ spec: - name: schemas resources: requests: - cpu: "20m" + cpu: "100m" memory: "128Mi" limits: memory: "768Mi" -- 2.52.0