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

Compare commits

base: admin/turingpi:9b24978342cdd50d29295c65c821338ced20468e
Branches Tags
admin/turingpi:master
...
compare: admin/turingpi:1b3f34a43294033329d77a4b33533fa55e57ed19
Branches Tags
admin/turingpi:master

2 Commits
9b24978342 ... 1b3f34a432

Author SHA1 Message Date
gilgamezh 1b3f34a432 build: upgrade qbittorrent 5.1.4-r3-ls453 -> 5.2.1_v2.0.12-ls459 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 2026-05-31 10:59:16 +02:00
gilgamezh 261aebfd10 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>
 2026-05-31 10:59:03 +02:00
2 changed files with 7 additions and 1 deletions
Expand all files Collapse all files
helm-values/qbittorrent_values.yaml
+1 -1
View File
@@ -4,7 +4,7 @@ replicaCount: 1
qbittorrent:
image:
repository: lscr.io/linuxserver/qbittorrent
tag: "5.1.4-r3-ls453"
tag: "5.2.1_v2.0.12-ls459"
pullPolicy: Always
env:
- name: PUID
non_argo_values/gitea_values.yaml
+6
View File
@@ -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: