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

@@ -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: