From 890809c91c12c5558e40acca6494ed1f4780a4ad Mon Sep 17 00:00:00 2001 From: CTO Agent Date: Sun, 16 Aug 2026 12:54:26 +0000 Subject: [PATCH] fix(monitoring): Loki uses Recreate strategy for RWO PVC rollouts (DEV-483) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit RollingUpdate deadlocks the Loki rollout because loki-storage-encrypted is a Hetzner CSI RWO volume — the new pod on worker-2 cannot attach the PVC while the old pod on worker-1 still holds it. Recreate drains the old pod first so the CSI detaches the volume cleanly. Same pattern as the Harbor fix (commit 56e598f). Co-Authored-By: Paperclip --- apps/monitoring/loki-deployment.yaml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/apps/monitoring/loki-deployment.yaml b/apps/monitoring/loki-deployment.yaml index ef2c662..4336dd4 100644 --- a/apps/monitoring/loki-deployment.yaml +++ b/apps/monitoring/loki-deployment.yaml @@ -10,11 +10,12 @@ spec: selector: matchLabels: app: loki + # loki-storage-encrypted is RWO on hcloud-volumes-encrypted, so a rolling + # update deadlocks (new pod cannot attach the PVC while the old pod holds + # it). Recreate drops the old pod first so the CSI detaches the volume + # before the new pod tries to attach it. Same pattern as harbor's RWO fix. strategy: - type: RollingUpdate - rollingUpdate: - maxSurge: 25% - maxUnavailable: 25% + type: Recreate template: metadata: labels: