From 56e598f66c099504132fa0e4d66b0c764b075c3b Mon Sep 17 00:00:00 2001 From: CTO Agent Date: Sat, 8 Aug 2026 15:51:06 +0000 Subject: [PATCH] fix(harbor): set updateStrategy=Recreate for RWO PVC rollouts Harbor's jobservice and registry Deployments have RWO PVCs (Hetzner Cloud Volumes). The default RollingUpdate strategy deadlocks: the new pod cannot attach the volume while the old pod still holds it on a different node. This has left the harbor Argo CD Application in a Degraded state since 2026-08-07. The goharbor chart exposes a top-level updateStrategy specifically for this case ("Set it as Recreate when RWM for volumes isn't supported"). Refs DEV-458. Co-Authored-By: Paperclip --- apps/harbor/values.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/apps/harbor/values.yaml b/apps/harbor/values.yaml index c9e4e72..e8c136f 100644 --- a/apps/harbor/values.yaml +++ b/apps/harbor/values.yaml @@ -17,6 +17,12 @@ harbor: externalURL: https://harbor.basicstack.de + # Hetzner Cloud Volumes are ReadWriteOnce; RollingUpdate deadlocks on + # jobservice/registry rollouts because the new pod cannot attach the PVC + # while the old pod still holds it on another node (DEV-458). + updateStrategy: + type: Recreate + persistence: enabled: true resourcePolicy: keep