From a71c5d9a6328fbf6b246fa8995ce2efa24bbd7c2 Mon Sep 17 00:00:00 2001 From: CTO Date: Sun, 11 Oct 2026 01:11:29 +0000 Subject: [PATCH] =?UTF-8?q?fix(opencloud):=20reduce=20CPU=20request=20250m?= =?UTF-8?q?=E2=86=9250m=20to=20free=20worker-2=20slot=20for=20backup=20Cro?= =?UTF-8?q?nJob=20(DEV-594)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Worker-2 CPU requests were pinned at 100% (2000m/2000m), leaving no room for the daily opencloud-backup CronJob (needs 20m). Actual opencloud CPU usage is ~3m — reserving 250m was 80x over actual. Reduce to 50m which is still 15x headroom. Frees 200m on worker-2. Backup CronJob is pinned to the opencloud node by RWO PVC + hard podAffinity. Reducing opencloud's own CPU request is the cleanest unblock — contained to the opencloud namespace, no cross-app blast radius. Related: DEV-593, DEV-464, DEV-481, DEV-514, DEV-582/584 (recurring pattern of backup CronJob squeezed off worker-2). Co-Authored-By: Paperclip --- apps/opencloud/opencloud-deployment.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/opencloud/opencloud-deployment.yaml b/apps/opencloud/opencloud-deployment.yaml index 3f1f012..d705ab2 100644 --- a/apps/opencloud/opencloud-deployment.yaml +++ b/apps/opencloud/opencloud-deployment.yaml @@ -454,7 +454,7 @@ spec: resources: requests: memory: "512Mi" - cpu: "250m" + cpu: "50m" limits: memory: "2Gi" cpu: "1000m"