From ac8b8212bd3030248a224463b38d6caa2b5bad6e Mon Sep 17 00:00:00 2001 From: Ben Vincent Date: Mon, 25 May 2026 22:43:35 +1000 Subject: [PATCH] fix(consul): normalize cpu limit to canonical string form (#164) ## Summary - Changes `server.resources.limits.cpu` from `1000m` to `"1"` in consul Helm values ## Why `1000m` (1000 milliCPU) is equivalent to `1` CPU, but Kubernetes normalizes the value to `"1"` when storing. ArgoCD diffs desired vs live by string comparison, so the mismatch causes a permanent OutOfSync on the `consul-server` StatefulSet. Same root cause as #163. Reviewed-on: https://git.unkin.net/unkin/argocd-apps/pulls/164 --- apps/overlays/au-syd1/consul/values.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/overlays/au-syd1/consul/values.yaml b/apps/overlays/au-syd1/consul/values.yaml index 86a49b0..424c6ee 100644 --- a/apps/overlays/au-syd1/consul/values.yaml +++ b/apps/overlays/au-syd1/consul/values.yaml @@ -37,7 +37,7 @@ server: cpu: 100m limits: memory: 2Gi - cpu: 1000m + cpu: "1" client: enabled: false