fix(ci_init_gitops): add limits.cpu to staging override-values.yaml template#94
Open
joaoffnascimento wants to merge 1 commit into
Open
fix(ci_init_gitops): add limits.cpu to staging override-values.yaml template#94joaoffnascimento wants to merge 1 commit into
joaoffnascimento wants to merge 1 commit into
Conversation
…emplate 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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problema
Quando
ci_init_gitops.ymlcriastaging/override-values.yamlpara um serviço novo, o template gerado omitelimits.cpu:O Kubernetes herda
limits.cpudobase.yamldo serviço (pode ser 80m ou 85m). Comorequests.cpu: 150m > limits.cpu: 80m, o K8s rejeita e o ArgoCD fica em OutOfSync.Fix
Adicionar
limits.cpu: 150mexplicitamente no template:Impacto observado
8 serviços ficaram
OutOfSyncno ArgoCD staging após migração GitOps:Workaround aplicado em
kube-apps-definitionsadicionandolimits.cpu: 150mmanualmente nos overrides afetados.