From 44ca1f1e5198a940a3dc5f21d0545378d6d1d9c9 Mon Sep 17 00:00:00 2001 From: Alert Fix Agent Date: Tue, 21 Jul 2026 11:43:51 +0000 Subject: [PATCH] fix: [alert] KubeDaemonSetRolloutStuck (crowdsec) (#325) --- kubernetes/infrastructure/crowdsec/helmrelease.yaml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/kubernetes/infrastructure/crowdsec/helmrelease.yaml b/kubernetes/infrastructure/crowdsec/helmrelease.yaml index f8508e2b..50404806 100644 --- a/kubernetes/infrastructure/crowdsec/helmrelease.yaml +++ b/kubernetes/infrastructure/crowdsec/helmrelease.yaml @@ -39,8 +39,16 @@ spec: # kubernetes/infrastructure/openbao/rotation/crowdsec-bouncer-key.yaml. secret.reloader.stakater.com/reload: crowdsec-bouncer-key persistentVolume: + # data holds the machine-registration DB (crowdsec.db). LAPI uses + # strategy: Recreate, so any pod recreation (chart bump, the + # Reloader restart above, etc.) previously wiped this ephemeral + # store and permanently invalidated every agent's registration + # (issue #325: all 3 crowdsec-agent daemonset pods CrashLoopBackOff + # with "machine not found" after a LAPI recreation, since their + # once-run init container can't re-register without their own + # pod being recreated too). data: - enabled: false + enabled: true config: enabled: false env: -- 2.54.0