fix(monitoring): Loki uses Recreate strategy for RWO PVC rollouts (DEV-483)
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 <noreply@paperclip.ing>
This commit is contained in:
parent
e4a7e5629a
commit
890809c91c
1 changed files with 5 additions and 4 deletions
|
|
@ -10,11 +10,12 @@ spec:
|
||||||
selector:
|
selector:
|
||||||
matchLabels:
|
matchLabels:
|
||||||
app: loki
|
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:
|
strategy:
|
||||||
type: RollingUpdate
|
type: Recreate
|
||||||
rollingUpdate:
|
|
||||||
maxSurge: 25%
|
|
||||||
maxUnavailable: 25%
|
|
||||||
template:
|
template:
|
||||||
metadata:
|
metadata:
|
||||||
labels:
|
labels:
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue