From ef4a1d7ce23d12d51fbee92697318df30d32b403 Mon Sep 17 00:00:00 2001 From: Daniel Sy Date: Fri, 19 Jun 2026 09:58:50 +0200 Subject: [PATCH] =?UTF-8?q?fix(observability):=20=F0=9F=90=9B=20disable=20?= =?UTF-8?q?crds.cleanup=20hook=20in=20victoria-metrics-operator?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Pre-upgrade cleanup hook uses bitnami/kubectl and spawns on every ArgoCD sync. Dev cluster nodes are at 99% CPU / pod limit — hook pod cannot be scheduled, blocking the entire sync indefinitely. Disabling cleanup.enabled prevents the hook Job from being created. CRD cleanup is safe to skip on a fresh bootstrap where no old CRDs exist. --- .../stacks/observability/victoria-k8s-stack/values.yaml | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/otc/dev.t09.de/stacks/observability/victoria-k8s-stack/values.yaml b/otc/dev.t09.de/stacks/observability/victoria-k8s-stack/values.yaml index d407910..ca0b671 100644 --- a/otc/dev.t09.de/stacks/observability/victoria-k8s-stack/values.yaml +++ b/otc/dev.t09.de/stacks/observability/victoria-k8s-stack/values.yaml @@ -28,10 +28,7 @@ victoria-metrics-operator: crds: plain: true cleanup: - enabled: true - image: - repository: bitnami/kubectl - pullPolicy: IfNotPresent + enabled: false # disabled: cleanup hook can't schedule on resource-constrained nodes (Insufficient cpu / Too many pods) serviceMonitor: enabled: true operator: