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 <noreply@paperclip.ing>
This commit is contained in:
parent
64f61981ba
commit
56e598f66c
1 changed files with 6 additions and 0 deletions
|
|
@ -17,6 +17,12 @@ harbor:
|
||||||
|
|
||||||
externalURL: https://harbor.basicstack.de
|
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:
|
persistence:
|
||||||
enabled: true
|
enabled: true
|
||||||
resourcePolicy: keep
|
resourcePolicy: keep
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue