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.
This commit is contained in:
Ryan Lerch
2025-10-14 18:26:43 +10:00
parent bd743bc1d7
commit 720c224107

View File

@@ -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