From 7fdeacffb89e48de3739ddc99ae280a58890eb0c Mon Sep 17 00:00:00 2001 From: mr-forust Date: Tue, 6 Oct 2026 19:29:30 +0200 Subject: [PATCH] feat(monitoring): stand down Prometheus server during VM trial vmagent scrapes and remote-writes to VictoriaMetrics, so the Prometheus server scales to 0. Encoded as prometheusSpec.replicas in values instead of a kubectl patch, so helm keeps owning spec.replicas and Helm 4 server-side apply stops conflicting with the kubectl-patch field manager. --- prometheus-stack/k8s/grafana-values.yaml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/prometheus-stack/k8s/grafana-values.yaml b/prometheus-stack/k8s/grafana-values.yaml index 2a2f436..56acb32 100644 --- a/prometheus-stack/k8s/grafana-values.yaml +++ b/prometheus-stack/k8s/grafana-values.yaml @@ -60,6 +60,10 @@ grafana: prometheus: prometheusSpec: + # VM trial: vmagent scrapes and remote-writes to VictoriaMetrics, so the + # Prometheus server itself stands down. Encoded here (not a kubectl patch) + # so helm keeps owning spec.replicas and upgrades do not conflict on it. + replicas: 0 retention: 60d retentionSize: 32GB storageSpec: