admin/turingpi
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ops(gitea): Recreate strategy to avoid RWO upgrade deadlock

Browse Source 
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>
This commit is contained in:
gilgamezh
2026-05-31 10:59:03 +02:00
parent 9b24978342
commit 261aebfd10
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
non_argo_values/gitea_values.yaml
+6
View File
@@ -4,6 +4,12 @@
# Single replica for homelab # Single replica for homelab
replicaCount: 1 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 configuration - LoadBalancer for direct access
service: service:
http: http: