From 28844e50bead780288cb81a0d4ccda8c89cc6c4a Mon Sep 17 00:00:00 2001
From: Sebastian Nickel <nick@nine.ch>
Date: Mon, 13 Apr 2026 10:18:37 +0200
Subject: [PATCH] use at least 2 replicas for the nameserver

Currently there is just 1 replica of the nameserver being deployed. To allow for more availability, we increase to 2 and add try to spread the pods over multiple nodes.
---
 .../deploy/manifests/nameserver/deploy.yaml           | 11 +++++++++--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/cmd/k8s-operator/deploy/manifests/nameserver/deploy.yaml b/cmd/k8s-operator/deploy/manifests/nameserver/deploy.yaml
index 57ad783755453..95e98a845f430 100644
--- a/cmd/k8s-operator/deploy/manifests/nameserver/deploy.yaml
+++ b/cmd/k8s-operator/deploy/manifests/nameserver/deploy.yaml
@@ -3,13 +3,13 @@ kind: Deployment
 metadata:
   name: nameserver 
 spec:
-  replicas: 1
+  replicas: 2
   revisionHistoryLimit: 5
   selector:
     matchLabels:
       app: nameserver
   strategy:
-    type: Recreate
+    type: RollingUpdate
   template:
     metadata:
       labels:
@@ -33,6 +33,13 @@ spec:
         volumeMounts:
         - name: dnsrecords
           mountPath: /config
+      topologySpreadConstraints:
+      - maxSkew: 1
+        topologyKey: kubernetes.io/hostname
+        whenUnsatisfiable: ScheduleAnyway
+        labelSelector:
+          matchLabels:
+            app: nameserver
       restartPolicy: Always
       serviceAccount: nameserver
       serviceAccountName: nameserver