From 10bf0aaf707709dbcd7c10543d05612e8d719c45 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jo=C3=A3o=20Felipe=20Fonseca=20Nascimento?=
 <thecurrentuser@live.com>
Date: Wed, 3 Jun 2026 11:43:23 -0300
Subject: [PATCH] fix(ci_init_gitops): add limits.cpu to staging
 override-values.yaml template
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

When ci_init_gitops creates staging/override-values.yaml for a new service,
it was omitting limits.cpu. Kubernetes then inherits limits.cpu from base.yaml
(which can be as low as 80m), while requests.cpu is set to 150m.
This causes: requests.cpu (150m) > limits.cpu (80m) → K8s validation error → ArgoCD OutOfSync.

Fix: explicitly set limits.cpu: 150m in the generated template.
---
 .github/workflows/ci_init_gitops.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.github/workflows/ci_init_gitops.yml b/.github/workflows/ci_init_gitops.yml
index eb153fd..a0c2430 100644
--- a/.github/workflows/ci_init_gitops.yml
+++ b/.github/workflows/ci_init_gitops.yml
@@ -111,6 +111,7 @@ jobs:
             cat > "$SERVICE/$ENV/override-values.yaml" << 'EOF'
           resources:
             limits:
+              cpu: 150m
               memory: 256Mi
             requests:
               cpu: 150m