Jeffrey/Kubernetes-Manifests
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

victoria-metrics: pin back to chart 0.77.0 after a failed 0.91.2 upgrade

Browse Source 
The 0.91.2 bump had been sitting in Git unapplied because the app could not
generate manifests. Once the values path was fixed it applied, and Grafana
crash-looped on "Datasource provisioning error: data source not found".
Rolled back; Grafana and all 35 VMRules are healthy again on 0.77.0.

0.91.2 also moves the default dashboards and rules out of the Helm render
into a runtime sync-job, so upgrading needs a values migration and a
verified datasource config rather than a version bump.
This commit is contained in:
Jeffrey
2026-08-29 18:39:49 +02:00
parent 02c43d8b85
commit a775c8b837
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
infra/argocd/applications/victoria-metrics-application.yaml
+7 -1
View File
@@ -8,7 +8,13 @@ spec:
sources: sources:
- repoURL: https://victoriametrics.github.io/helm-charts/ - repoURL: https://victoriametrics.github.io/helm-charts/
chart: victoria-metrics-k8s-stack chart: victoria-metrics-k8s-stack
targetRevision: 0.91.2 # Pinned at 0.77.0. 0.91.2 was tried on 2026-08-29 and rolled back:
# Grafana crash-looped on "Datasource provisioning error: data source
# not found". The chart also moves dashboards and the 35 default VMRules
# out of the Helm render and into a runtime sync-job, so the upgrade
# needs a values migration and a verified datasource config, not a
# version bump.
targetRevision: 0.77.0
helm: helm:
# Release name kept short to avoid label length >63 chars on alertmanager StatefulSet pods # Release name kept short to avoid label length >63 chars on alertmanager StatefulSet pods
releaseName: vm releaseName: vm