From 50bf1b1cda71c034c81971ea3eea32966fe66279 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 10 May 2026 09:55:01 +0300 Subject: navidrome: use Recreate strategy SQLite on RWO PVC can only have one writer. RollingUpdate keeps the old pod alive until the new pod is Ready, but the new pod blocks indefinitely on SQLite open because the old pod still holds the db-shm/db-wal lock. Recreate kills the old pod first. Amp-Thread-ID: https://ampcode.com/threads/T-019e109f-fa43-7467-bb0b-1a4a2d3d0b9e Co-authored-by: Amp --- f3s/navidrome/helm-chart/templates/deployment.yaml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/f3s/navidrome/helm-chart/templates/deployment.yaml b/f3s/navidrome/helm-chart/templates/deployment.yaml index c7ddbf7..5a3862e 100644 --- a/f3s/navidrome/helm-chart/templates/deployment.yaml +++ b/f3s/navidrome/helm-chart/templates/deployment.yaml @@ -5,6 +5,11 @@ metadata: namespace: services spec: replicas: 1 + # SQLite DB on RWO PVC: only one writer at a time. Use Recreate so the + # old pod releases the DB lock before the new pod starts; otherwise the + # new pod blocks indefinitely on the SQLite open. + strategy: + type: Recreate selector: matchLabels: app: navidrome -- cgit v1.2.3