fix: switch backend deployment to RollingUpdate for zero downtime

maxUnavailable=0 ensures old pod stays up until new pod passes
readiness probes. maxSurge=1 allows one extra pod during rollout.
This commit is contained in:
2026-02-27 13:43:04 +01:00
parent ac892720df
commit 2def99d163

View File

@@ -10,7 +10,10 @@ spec:
replicas: {{ .Values.replicaCount }}
{{- end }}
strategy:
type: Recreate
type: RollingUpdate
rollingUpdate:
maxUnavailable: 0
maxSurge: 1
selector:
matchLabels:
{{- include "marktvogt-backend.selectorLabels" . | nindent 6 }}