Update scheduling stragety

With 3 replicas, 3 control plane nodes, and required anti-affinity,
there might not be room for a 4th pod during rollout.

Setting maxSurge: 0 and maxUnavailable: 1 kills one pod first, then
schedules the replacement.

Author: dcelasun

manifest.example.yaml

@@ -68,6 +68,11 @@ metadata:
     app: node-taint-controller
 spec:
   replicas: 3
+  strategy:
+    type: RollingUpdate
+    rollingUpdate:
+      maxSurge: 0
+      maxUnavailable: 1
   selector:
     matchLabels:
       app: node-taint-controller