From f83d73c06d7faadee2d20ef6982872ab1d539b26 Mon Sep 17 00:00:00 2001
From: vikingowl <christian@nachtigall.dev>
Date: Sun, 22 Feb 2026 12:00:23 +0100
Subject: [PATCH] fix(deploy): set maxSurge=0 to fit within ResourceQuota
 during rollout

With 900m/1000m CPU limits used, rolling updates fail because the
new pod cannot be created alongside the old one. Setting maxSurge=0
and maxUnavailable=1 kills the old pod first, avoiding quota exhaustion
at the cost of brief downtime during deploys.
---
 web/deploy/helm/templates/deployment.yaml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/web/deploy/helm/templates/deployment.yaml b/web/deploy/helm/templates/deployment.yaml
index ba89b98..df3e791 100644
--- a/web/deploy/helm/templates/deployment.yaml
+++ b/web/deploy/helm/templates/deployment.yaml
@@ -9,6 +9,11 @@ spec:
   {{- if not .Values.autoscaling.enabled }}
   replicas: {{ .Values.replicaCount }}
   {{- end }}
+  strategy:
+    type: RollingUpdate
+    rollingUpdate:
+      maxSurge: 0
+      maxUnavailable: 1
   selector:
     matchLabels:
       {{- include "marktvogt-web.selectorLabels" . | nindent 6 }}