From 720c224107c13a044e716bf2a0cd827f9652f08f Mon Sep 17 00:00:00 2001
From: Ryan Lerch <rlerch@redhat.com>
Date: Tue, 14 Oct 2025 18:26:43 +1000
Subject: [PATCH] Fix Forgejo deployment strategy to prevent queue lock
 conflicts

Change maxSurge from 100% to 0 and maxUnavailable from 0 to 1 to ensure old pod terminates before new pod starts, preventing LevelDB queue lock conflicts when email notifications are enabled.
---
 roles/openshift-apps/forgejo/templates/values.yaml.j2 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/roles/openshift-apps/forgejo/templates/values.yaml.j2 b/roles/openshift-apps/forgejo/templates/values.yaml.j2
index bcdd21c0cd..94dc3d657e 100644
--- a/roles/openshift-apps/forgejo/templates/values.yaml.j2
+++ b/roles/openshift-apps/forgejo/templates/values.yaml.j2
@@ -34,8 +34,8 @@ replicaCount: 1
 strategy:
   type: 'RollingUpdate'
   rollingUpdate:
-    maxSurge: '100%'
-    maxUnavailable: 0
+    maxSurge: 0
+    maxUnavailable: 1
 
 ## @param clusterDomain cluster domain
 clusterDomain: cluster.local