From 54e7a25f93a52cc90d41b7922864e1e0dcd5379d Mon Sep 17 00:00:00 2001
From: "Dustin C. Hatch" <dustin@hatch.name>
Date: Mon, 22 Jan 2024 16:43:46 -0600
Subject: [PATCH] v-m: vmstorage: Remove startup/ready probes

Kubernetes will not start additional Pods in a StatefulSet until the
existing ones are Ready.  This means that if there is a problem bringing
up, e.g. `vmstorage-0`, it will never start `vmstorage-1` or
`vmstorage-2`.  Since this pretty much defeats the purpose of having a
multi-node `vmstorage` cluster, we have to remove the readiness probe,
so the Pods will be Ready as soon as they start.  If there is a problem
with one of them, it will matter less, as the others can still run.
---
 victoria-metrics/vmstorage.yaml | 11 -----------
 1 file changed, 11 deletions(-)

diff --git a/victoria-metrics/vmstorage.yaml b/victoria-metrics/vmstorage.yaml
index 50c2d4a..f9b094f 100644
--- a/victoria-metrics/vmstorage.yaml
+++ b/victoria-metrics/vmstorage.yaml
@@ -50,17 +50,6 @@ spec:
           name: vmselect
         - containerPort: 8482
           name: http
-        readinessProbe: &probe
-          httpGet:
-            port: http
-            path: /health
-          periodSeconds: 60
-        startupProbe:
-          <<: *probe
-          periodSeconds: 1
-          successThreshold: 1
-          failureThreshold: 30
-          timeoutSeconds: 1
         securityContext:
           runAsNonRoot: true
           readOnlyRootFilesystem: true