From 261aebfd10e08127b8c51d9d7626a93a9f5d9990 Mon Sep 17 00:00:00 2001
From: gilgamezh <mail@gilgamezh.me>
Date: Sun, 31 May 2026 10:59:03 +0200
Subject: [PATCH] ops(gitea): Recreate strategy to avoid RWO upgrade deadlock

Bumped gitea helm chart 12.4.0->12.6.0 (app 1.24.6->1.26.1). The chart
default RollingUpdate (maxSurge 100%/maxUnavailable 0) surges a second pod
that can't mount the single RWO NFS PVC, deadlocking 'helm upgrade --wait'.
Recreate avoids it.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---
 non_argo_values/gitea_values.yaml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/non_argo_values/gitea_values.yaml b/non_argo_values/gitea_values.yaml
index 711b0b3..34961ed 100644
--- a/non_argo_values/gitea_values.yaml
+++ b/non_argo_values/gitea_values.yaml
@@ -4,6 +4,12 @@
 # Single replica for homelab
 replicaCount: 1
 
+# Gitea data lives on a single RWO NFS PVC, so two pods can't run at once.
+# The chart default (RollingUpdate maxSurge 100%/maxUnavailable 0) surges a
+# second pod and deadlocks on upgrade -- use Recreate instead.
+strategy:
+  type: Recreate
+
 # Service configuration - LoadBalancer for direct access
 service:
   http: