You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BUGFIX: fix templates/route.yaml and templates/ingress.yaml failing with vm.operator.kind: appKey "alertmanager" is not vm/vl/vt-prefixed when alertmanager.route.enabled: true or alertmanager.ingress.enabled: true is set. Regression from the victoria-metrics-common 0.4.* bump in v0.95.1, since alertmanager is the only top-level component key that isn't itself vm/vl/vt-prefixed (see #3270).
bump victoria-metrics-common dependency to 0.4.*. Resource names are unchanged.
BUGFIX: preserve user-supplied .Values.alertmanager.config.templates entries instead of overwriting them with the default /etc/vm/templates/**/*.tmpl glob, so custom template paths are no longer silently dropped from the generated config Secret (see #3266).
Configuration
📅 Schedule: (UTC)
Branch creation
"before 9am on tuesday"
Automerge
At any time (no schedule defined)
🚦 Automerge: Disabled because a matching PR was automerged previously.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
If you want to rebase/retry this PR, check this box
Updates VictoriaMetrics stack and operator CRD Helm charts.
No findings
Confidence 4/5 · medium risk: The diff is two patch-level chart bumps (k8s-stack 0.95.0 to 0.95.2 across three monitoring releases, operator CRDs 0.15.0 to 0.15.1), and the review found no problems in them. The stack pulls in a victoria-metrics-common 0.3 to 0.4 minor step that the review checked only for naming, not for template or value-schema changes, so I hold the score just below 5.
Approved
Summary
The change updates all three VictoriaMetrics stack releases to 0.95.2 and the dedicated CRD release to 0.15.1. The upstream fixes are compatible with the configured components, and the CRD update preserves the existing schemas while improving manifest serialization.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.95.0→0.95.20.96.00.15.0→0.15.1Release Notes
VictoriaMetrics/helm-charts (victoria-metrics-k8s-stack)
v0.95.2Compare Source
Release notes for version 0.95.2
Release date: 07 Oct 2026
templates/route.yamlandtemplates/ingress.yamlfailing withvm.operator.kind: appKey "alertmanager" is not vm/vl/vt-prefixedwhenalertmanager.route.enabled: trueoralertmanager.ingress.enabled: trueis set. Regression from thevictoria-metrics-common0.4.* bump in v0.95.1, sincealertmanageris the only top-level component key that isn't itself vm/vl/vt-prefixed (see #3270).v0.95.1Compare Source
Release notes for version 0.95.1
Release date: 07 Oct 2026
victoria-metrics-commondependency to0.4.*. Resource names are unchanged..Values.alertmanager.config.templatesentries instead of overwriting them with the default/etc/vm/templates/**/*.tmplglob, so custom template paths are no longer silently dropped from the generated configSecret(see #3266).Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled because a matching PR was automerged previously.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.