chore(deps): update helm release victoria-metrics-k8s-stack to v0.95.0 #7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/victoria-metrics-k8s-stack-0.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.91.0->0.95.0Release Notes
VictoriaMetrics/helm-charts (victoria-metrics-k8s-stack)
v0.95.0Compare Source
Release notes for version 0.95.0
Release date: 28 Sep 2026
v0.94.0Compare Source
Release notes for version 0.94.0
Release date: 28 Sep 2026
v0.93.0Compare Source
Release notes for version 0.93.0
Release date: 20 Sep 2026
syncJob.imagePullSecrets, falling back toglobal.imagePullSecrets. The sync-job Pod had no way to receive pull secrets, sosyncJob.image.repositorycould not point at a private registry or mirror.v0.92.1Compare Source
Release notes for version 0.92.1
Release date: 07 Sep 2026
GrafanaDatasourceplugin entries missing a requiredversionfield, which grafana-operator rejects. Defaults tolatestwhen the datasource doesn't set one. See #3200v0.92.0Compare Source
Release notes for version 0.92.0
Release date: 07 Sep 2026
defaultRules.groups[*].enabledmay now be a template expression (e.g.{{ .Values.kubeScheduler.enabled }}), likedefaultDashboards.dashboards[*].enabledalready was. DisablingkubeApiServer,kubeControllerManager,kubeScheduler, orkubeletnow also disables their alerting rule groups, so alerts no longer fire on scrape targets that were never enabled. See #3197alertmanager.rulesgroup keeping upstream kube-prometheus'sjob="alertmanager-main",namespace="monitoring"selectors, which never match this chart's VMAlertmanager. The sync-job now rewrites both to a regexp matching this chart's VMAlertmanager(s) via a newlabelRewritesoption (alongside the existingjobNamespaces), configurable underdefaultRules.labelRewrites/defaultRules.groups.<name>.labelRewrites; values may be template expressions (e.g.{{ .Release.Namespace }}), rendered before use. See #11517pluginssection missing fromGrafanaDatasourceCRs for datasources whose type requires a Grafana plugin not already listed ingrafana.plugins. See #3181global.versions(metrics/logs/traces/anomaly/alertmanager), shared automatically with the embedded operator chart's ownglobal.versions, so CRs created outside this chart default to the same version the chart deploys instead of the operator's own baked-in default. See #3186v0.91.2Compare Source
Release notes for version 0.91.2
Release date: 22 Aug 2026
OUTPUT=-generating malformed YAML for ConfigMap manifests. See #3169v0.91.1Compare Source
Release notes for version 0.91.1
Release date: 21 Aug 2026
defaultRules.groups.<name>.specoverrides (e.g.interval). Per-group spec fields are now merged on top of the common group spec and applied to the generated VMRule. See #3166Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.