feat(container): update image victoria-metrics-k8s-stack ( 0.85.3 → 0.86.0 )#3999
Merged
Merged
Conversation
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
victoria-metrics-k8s-stack: v0.85.3 → v0.85.4
Verdict: Safe to merge
Summary:
Patch bump introducing improved garbage collection for sync-job managed resources (ConfigMaps, GrafanaDashboards, VMRules). The feature is controlled by syncJob.useOwnerReferences (default true), which automatically sets owner references to enable Kubernetes garbage collection.
Impact Assessment:
- No breaking changes or deprecations
- No config changes required in
monitoring/victoria-metrics/victoria-metrics.yaml - The default behavior (owner references enabled) is beneficial and improves cluster hygiene when the release is uninstalled
- All monitored components (vmsingle, alertmanager, vmalert, vmagent) continue to work as before
Sources consulted:
Claude Review Usage
|
renovate
Bot
force-pushed
the
renovate/victoria-metrics-k8s-stack-0.x
branch
from
June 25, 2026 19:46
51d56f3 to
f9affb3
Compare
renovate
Bot
changed the title
claude
Bot
dismissed
their stale review
June 25, 2026 19:47
Superseded by updated review covering 0.85.5
There was a problem hiding this comment.
victoria-metrics-k8s-stack: v0.85.3 → v0.85.5
Verdict: Safe to merge
Summary:
Patch bump covering two minor releases with bug fixes and improved resource cleanup. No breaking changes or configuration updates required.
Changes included:
- v0.85.4 (24 Jun 2026): Adds owner references on managed ConfigMaps, GrafanaDashboards, and VMRules for automatic garbage collection. Controlled by
syncJob.useOwnerReferences(defaulttrue). - v0.85.5 (25 Jun 2026): Fixes sync-job failing to patch cluster variable filters in dashboards stored as structured objects (map form).
Impact Assessment:
- AppVersion remains v1.146.0 (chart-only patch)
- No breaking changes or deprecations
- Current config in
monitoring/victoria-metrics/victoria-metrics.yamlusesdefaultDashboards: enabled: true, so v0.85.5 fix is directly relevant - No explicit
syncJobconfiguration needed; defaults apply - Owner references feature (v0.85.4) is beneficial for cluster cleanup and enabled by default
- All monitored components (vmsingle, alertmanager, vmalert, vmagent) continue to work as before
Sources consulted:
renovate
Bot
force-pushed
the
renovate/victoria-metrics-k8s-stack-0.x
branch
from
June 25, 2026 19:51
f9affb3 to
8d015aa
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/victoria-metrics-k8s-stack-0.x
branch
from
June 26, 2026 23:36
8d015aa to
d5aac64
Compare
claude
Bot
dismissed
their stale review
June 26, 2026 23:37
Superseded by updated review covering v0.85.6
There was a problem hiding this comment.
victoria-metrics-k8s-stack: v0.85.3 → v0.85.6
Verdict: Safe to merge
Summary:
Patch bump covering three minor releases with bug fixes and improved resource cleanup. No breaking changes or configuration updates required.
Changes included:
- v0.85.4 (24 Jun 2026): Adds owner references on managed ConfigMaps, GrafanaDashboards, and VMRules for automatic garbage collection. Controlled by
syncJob.useOwnerReferences(defaulttrue). - v0.85.5 (25 Jun 2026): Fixes sync-job failing to patch cluster variable filters in dashboards stored as structured objects (map form).
- v0.85.6 (26 Jun 2026): Sync-job manifest generation mode support (OUTPUT env var); fixes $cluster variable injection in dashboards with no cluster template variable.
Impact Assessment:
- AppVersion remains v1.146.0 (chart-only patches)
- No breaking changes or deprecations
- Current config in
monitoring/victoria-metrics/victoria-metrics.yamlusesdefaultDashboards: enabled: true, so v0.85.5 and v0.85.6 dashboard fixes are directly relevant - No explicit
syncJobconfiguration needed; defaults apply - Owner references feature (v0.85.4) is beneficial for cluster cleanup and enabled by default
- All monitored components (vmsingle, alertmanager, vmalert, vmagent) continue to work as before
Sources consulted:
- Renovate release notes in PR body (v0.85.4–v0.85.6)
- Local configuration review (
monitoring/victoria-metrics/victoria-metrics.yaml)
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/victoria-metrics-k8s-stack-0.x
branch
from
June 28, 2026 12:36
d5aac64 to
89f5a4f
Compare
There was a problem hiding this comment.
victoria-metrics-k8s-stack: v0.85.3 → v0.85.7
Verdict: Safe to merge
Summary:
Patch bump covering four minor releases with bug fixes, improved resource cleanup, and enhanced DNS configuration support. No breaking changes or configuration updates required.
Changes included:
- v0.85.4 (24 Jun 2026): Adds owner references on managed ConfigMaps, GrafanaDashboards, and VMRules for automatic garbage collection. Controlled by
syncJob.useOwnerReferences(defaulttrue). - v0.85.5 (25 Jun 2026): Fixes sync-job failing to patch cluster variable filters in dashboards stored as structured objects (map form).
- v0.85.6 (26 Jun 2026): Sync-job manifest generation mode support (OUTPUT env var); fixes $cluster variable injection in dashboards with no cluster template variable.
- v0.85.7 (28 Jun 2026): Sync-job now supports overriding dnsConfig and dnsPolicy; removed unsupported
vlandvtcluster parameters.
Impact Assessment:
- AppVersion remains v1.146.0 (chart-only patches)
- No breaking changes or deprecations
- Removed
vlandvtparameters were unsupported; verified not in use inmonitoring/victoria-metrics/victoria-metrics.yaml - DNS config overrides are opt-in (no config changes required)
- Current config uses
defaultDashboards: enabled: true, benefiting from v0.85.5 and v0.85.6 dashboard fixes - No explicit
syncJobconfiguration needed; defaults apply - Owner references feature (v0.85.4) is beneficial for cluster cleanup and enabled by default
- All monitored components (vmsingle, alertmanager, vmalert, vmagent) continue to work as before
Sources consulted:
- Renovate release notes in PR body (v0.85.4–v0.85.7)
- Local configuration review (
monitoring/victoria-metrics/victoria-metrics.yaml) - Repository code search (confirmed no usage of removed parameters)
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/victoria-metrics-k8s-stack-0.x
branch
from
June 29, 2026 13:52
89f5a4f to
39b7851
Compare
claude
Bot
dismissed
their stale review
June 29, 2026 13:53
Superseded by updated review for v0.85.8
There was a problem hiding this comment.
victoria-metrics-k8s-stack: v0.85.3 → v0.85.8
Verdict: Safe to merge
Summary:
Patch bump covering five minor releases with bug fixes, improved resource cleanup, enhanced DNS configuration support, and expanded sync-job environment variable support. No breaking changes or configuration updates required.
Changes included:
- v0.85.4 (24 Jun 2026): Adds owner references on managed ConfigMaps, GrafanaDashboards, and VMRules for automatic garbage collection. Controlled by
syncJob.useOwnerReferences(defaulttrue). - v0.85.5 (25 Jun 2026): Fixes sync-job failing to patch cluster variable filters in dashboards stored as structured objects (map form).
- v0.85.6 (26 Jun 2026): Sync-job manifest generation mode support (OUTPUT env var); fixes $cluster variable injection in dashboards with no cluster template variable.
- v0.85.7 (28 Jun 2026): Sync-job now supports overriding dnsConfig and dnsPolicy; removed unsupported
vlandvtcluster parameters. - v0.85.8 (29 Jun 2026): Adds support for additional env variables for syncJob.
Impact Assessment:
- AppVersion remains v1.146.0 (chart-only patches)
- No breaking changes or deprecations
- Removed
vlandvtparameters were unsupported; verified not in use inmonitoring/victoria-metrics/victoria-metrics.yaml - DNS config overrides are opt-in (no config changes required)
- Additional env variable support in 0.85.8 is purely additive (no defaults affected)
- Current config uses
defaultDashboards: enabled: true, benefiting from v0.85.5 and v0.85.6 dashboard fixes - No explicit
syncJobconfiguration needed; defaults apply - Owner references feature (v0.85.4) is beneficial for cluster cleanup and enabled by default
- All monitored components (vmsingle, alertmanager, vmalert, vmagent) continue to work as before
Sources consulted:
- Renovate release notes in PR body (v0.85.4–v0.85.8)
- Local configuration review (
monitoring/victoria-metrics/victoria-metrics.yaml) - Repository code search (confirmed no usage of removed parameters)
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/victoria-metrics-k8s-stack-0.x
branch
from
July 1, 2026 20:54
39b7851 to
c954bab
Compare
There was a problem hiding this comment.
victoria-metrics-k8s-stack: v0.85.3 → v0.85.9
Verdict: Safe to merge
Summary:
- Patch-level bump covering v0.85.4 through v0.85.9
- Underlying VictoriaMetrics app version (v1.146.0) unchanged
- Changes include sync-job owner references, Grafana dashboard variable fixes, dnsConfig/dnsPolicy support, and manifest generation mode
Not applicable to this repo:
- All sync-job changes (Grafana integration) — Grafana is disabled in the HelmRelease config
- Removal of unsupported vl/vt cluster parameters — not used in this config
Sources consulted:
- Renovate PR body with release notes v0.85.4 through v0.85.9
- Local HelmRelease config at monitoring/victoria-metrics/victoria-metrics.yaml
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/victoria-metrics-k8s-stack-0.x
branch
from
July 3, 2026 13:34
c954bab to
10a79b3
Compare
There was a problem hiding this comment.
victoria-metrics-k8s-stack: v0.85.3 → v0.85.10
Verdict: Safe to merge
Summary:
Patch bump covering v0.85.4 through v0.85.10 with bug fixes, improved resource cleanup, enhanced DNS configuration support, expanded sync-job environment variable support, and optional global label/annotation features. No breaking changes or configuration updates required.
New in v0.85.10:
- Added
global.extraLabelsandglobal.extraAnnotations— optional features for applying common labels and annotations to all workload resources and pod templates. Not used in current config; no action required. - Fixed vlagent spec delegating incorrectly to vmagent — not applicable; vlagent is not enabled in
monitoring/victoria-metrics/victoria-metrics.yaml.
Previous versions (v0.85.4–v0.85.9) — all safe:
- Owner references on managed resources for automatic garbage collection
- Sync-job Grafana dashboard variable fixes
- DNS config override support
- Sync-job manifest generation mode
- Additional env variable support
- All are additive or fix-only; grafana is disabled in this deployment
Impact Assessment:
- AppVersion remains v1.146.0 (chart-only patches)
- No breaking changes or deprecations
- Removed
vlandvtparameters (v0.85.7) were unsupported; verified not in use - All enabled components (vmsingle, alertmanager, vmalert, vmagent) continue to work without changes
- Default Helm version requirement is v3.14+ (compatible)
Sources consulted:
- Renovate release notes in PR body (v0.85.4–v0.85.10)
- Local configuration review (
monitoring/victoria-metrics/victoria-metrics.yaml) - Repository code search (confirmed no usage of removed parameters or vlagent)
….86.0 ) | datasource | package | from | to | | ---------- | -------------------------------------------------------------- | ------ | ------ | | docker | ghcr.io/victoriametrics/helm-charts/victoria-metrics-k8s-stack | 0.85.3 | 0.86.0 | Signed-off-by: Winston R. Milling <wrmilling@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/victoria-metrics-k8s-stack-0.x
branch
from
July 8, 2026 12:36
10a79b3 to
6d7b941
Compare
renovate
Bot
changed the title
There was a problem hiding this comment.
victoria-metrics-k8s-stack: v0.85.3 → v0.86.0
Verdict: Safe to merge ✅
Changes reviewed:
- Dependency updates: VictoriaMetrics components v1.147.0, VM Operator 0.66.2, Grafana 12.7.2
- Bug fixes: Fixed hardcoded datasources in dashboards when datasource variable is present, sync-job variable handling improvements
- New features: Manifest generation mode for sync-job, owner reference support for garbage collection, global
extraLabelsandextraAnnotationssupport - Removals: Unsupported
vlandvtcluster parameters (v0.85.7) — does not affect this repo's configuration
No breaking changes or deprecations identified. All changes are backwards-compatible. The standard victoria-metrics deployment in this repo (vmsingle, alertmanager, vmalert, vmagent) has no incompatibilities with this upgrade.
Sources consulted:
- v0.86.0 Release Notes
- v0.85.10 - v0.85.4 Release Notes (intermediate versions)
- Local HelmRelease configuration in
monitoring/victoria-metrics/victoria-metrics.yaml
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.85.3→0.86.0Release Notes
VictoriaMetrics/helm-charts (victoria-metrics-k8s-stack)
v0.86.0Release notes for version 0.86.0
Release date: 08 Jul 2026
v0.85.10Release notes for version 0.85.10
Release date: 03 Jul 2026
global.extraLabelsandglobal.extraAnnotationsto apply common labels and annotations to all workload resources and pod templatesvlagentspec incorrectly delegating tovmagentimplementation and overriding the image tag with the chartappVersioninstead of using the VictoriaLogs image tag configured invlagent.spec.image.tagv0.85.9Release notes for version 0.85.9
Release date: 01 Jul 2026
global.clusterLabelis customized, causing$clusterreferences in panel expressions to break. The variable name is now always kept ascluster; only the metric label in selectors is renamed to the configured value. See #3059.v0.85.8Release notes for version 0.85.8
Release date: 29 Jun 2026
v0.85.7Release notes for version 0.85.7
Release date: 28 Jun 2026
v0.85.6Release notes for version 0.85.6
Release date: 26 Jun 2026
OUTPUT=-(stdout) orOUTPUT=<file>to write all rendered ConfigMap/GrafanaDashboard/VMRule manifests as YAML instead of applying them to the cluster, allowing users to commit the output to a repository and deploy via GitOps tools in air-gapped environments. See #3040$clustervariable into dashboards that have no cluster template variable, causing Grafana to show "No data" or variable errors whenmulticluster: false. See #3042v0.85.5Release notes for version 0.85.5
Release date: 25 Jun 2026
v0.85.4Release notes for version 0.85.4
Release date: 24 Jun 2026
syncJob.useOwnerReferences(defaulttrue). See #3032Configuration
📅 Schedule: (in timezone America/Chicago)
🚦 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 was generated by Mend Renovate. View the repository job log.