From 86a83302b648d7e226e6420291b3815ef3df5a73 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mats=20T=C3=B6rnberg?= Date: Sun, 1 Nov 2026 18:01:08 +0100 Subject: [PATCH] Keep two DNS replicas under GitOps An imperative scale left kubectl owning the replica count while GitOps still declared one, causing apply conflicts. Declare two replicas so DNS remains available across a node failure and GitOps can reconcile the intended count. --- deploy/k8s/10-deployment.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/deploy/k8s/10-deployment.yaml b/deploy/k8s/10-deployment.yaml index e96d1e2..7790f58 100644 --- a/deploy/k8s/10-deployment.yaml +++ b/deploy/k8s/10-deployment.yaml @@ -15,7 +15,8 @@ spec: # across a reschedule). The flip side: the HPA does not work on a StatefulSet — the # controller and the autoscaler fight over the replica count — so scaling # means adding nodes and replicas here, not CPU targets. - replicas: 1 + # Keep DNS available if a node disappears and its pod cannot terminate. + replicas: 2 podManagementPolicy: Parallel selector: matchLabels: