From cde817845eff51a39c0808268d733ba82b5927b9 Mon Sep 17 00:00:00 2001 From: Nick Szaunig Date: Sat, 10 Oct 2026 04:08:07 +0200 Subject: [PATCH] chore(k8s): drop CPU and memory requests Requests are set to an explicit 0 instead of being removed, because Kubernetes defaults a missing request to the limit, which would reserve even more. Limits stay as an upper bound. Co-Authored-By: Claude Opus 5.5 (1M context) --- deploy/k8s/backend/deployment.yaml | 4 ++-- deploy/k8s/frontend/deployment.yaml | 4 ++-- deploy/k8s/postgres/statefulset.yaml | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/deploy/k8s/backend/deployment.yaml b/deploy/k8s/backend/deployment.yaml index e54b4b6..4292b96 100644 --- a/deploy/k8s/backend/deployment.yaml +++ b/deploy/k8s/backend/deployment.yaml @@ -48,8 +48,8 @@ spec: periodSeconds: 10 resources: requests: - cpu: 100m - memory: 128Mi + cpu: "0" + memory: "0" limits: cpu: 500m memory: 512Mi diff --git a/deploy/k8s/frontend/deployment.yaml b/deploy/k8s/frontend/deployment.yaml index b99d1ca..77088c3 100644 --- a/deploy/k8s/frontend/deployment.yaml +++ b/deploy/k8s/frontend/deployment.yaml @@ -30,8 +30,8 @@ spec: periodSeconds: 10 resources: requests: - cpu: 100m - memory: 128Mi + cpu: "0" + memory: "0" limits: cpu: 500m memory: 512Mi diff --git a/deploy/k8s/postgres/statefulset.yaml b/deploy/k8s/postgres/statefulset.yaml index b64f8a8..889cfa7 100644 --- a/deploy/k8s/postgres/statefulset.yaml +++ b/deploy/k8s/postgres/statefulset.yaml @@ -42,8 +42,8 @@ spec: periodSeconds: 10 resources: requests: - cpu: 250m - memory: 256Mi + cpu: "0" + memory: "0" limits: cpu: "1" memory: 1Gi