fix(crowdsec): use Recreate strategy for lapi to avoid RWO volume multi-attach
All checks were successful
Helm Charts / Detect changed charts (push) Successful in 49s
Helm Charts / Library charts tool (push) Has been skipped
Helm Charts / Application charts pgcat (push) Has been skipped

RollingUpdate with maxSurge>0 creates a new pod before terminating the old one,
causing a Multi-Attach error on the RWO PVCs (crowdsec-db-pvc, crowdsec-config-pvc).
Recreate terminates the old pod first, then starts the new one.
This commit is contained in:
2026-04-16 10:25:10 +02:00
parent 82a6eb0d85
commit 2367bd6cd7

View File

@@ -24,10 +24,7 @@ crowdsec: &crowdsec_config
value: Europe/Paris value: Europe/Paris
lapi: lapi:
strategy: strategy:
type: RollingUpdate type: Recreate
rollingUpdate:
maxUnavailable: 0
maxSurge: 1
env: env:
- name: TZ - name: TZ
value: Europe/Paris value: Europe/Paris
@@ -95,4 +92,4 @@ tool:
repo: https://crowdsecurity.github.io/helm-charts repo: https://crowdsecurity.github.io/helm-charts
chart: crowdsec chart: crowdsec
version: 0.20.1 version: 0.20.1
values: *crowdsec_config values: *crowdsec_config