From 2367bd6cd7208ef962244319e3e27c89e4a2cf39 Mon Sep 17 00:00:00 2001
From: arcodange <arcodange@gmail.com>
Date: Thu, 16 Apr 2026 10:25:10 +0200
Subject: [PATCH] fix(crowdsec): use Recreate strategy for lapi to avoid RWO
 volume multi-attach

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.
---
 crowdsec/values.yaml | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/crowdsec/values.yaml b/crowdsec/values.yaml
index 7156050..4bc52f8 100644
--- a/crowdsec/values.yaml
+++ b/crowdsec/values.yaml
@@ -24,10 +24,7 @@ crowdsec: &crowdsec_config
         value: Europe/Paris
   lapi:
     strategy:
-      type: RollingUpdate
-      rollingUpdate:
-        maxUnavailable: 0
-        maxSurge: 1
+      type: Recreate
     env:
       - name: TZ
         value: Europe/Paris
@@ -95,4 +92,4 @@ tool:
   repo: https://crowdsecurity.github.io/helm-charts
   chart: crowdsec
   version: 0.20.1
-  values: *crowdsec_config
\ No newline at end of file
+  values: *crowdsec_config