🎨 Renovate: Update victoriametrics/victoria-metrics Docker tag to v1.141.0

[SpiritLooper]

This PR contains the following updates:

Package	Update	Change	Pending
victoriametrics/victoria-metrics	minor	v1.140.0 → v1.141.0	v1.142.0

---

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/victoria-metrics)

v1.141.0

Compare Source

v1.141.0

Released at 2026-04-24

• SECURITY: upgrade base docker image (Alpine) from 3.23.3 to 3.23.4. See Alpine 3.23.4 release notes.

• FEATURE: all VictoriaMetrics components: add support for reading cpu/memory limits configured via systemd slices. Previously, only limits set directly on the process's own cgroup were detected. See #​10635. Thanks to @​andriibeee for the contribution.

• FEATURE: vmctl: improve error handling at opentsdb migration. See #​10797

• FEATURE: vmui: now Run query link on the Alerting Rules page correctly propagates the alert’s interval and evaluation time. See #​10366.

• FEATURE: alerts: add new MetricNameStatsCacheUtilizationIsTooHigh alerting rule to track overutilization of Metric names usage stats tracker (used in Cardinality Explorer). See #​10840.

• FEATURE: stream aggregation: add vm_streamaggr_counter_resets_total metric for total*, increase* and rate* outputs that is useful for aggregation behaviour tracking. These metrics help to identify issues described in Troubleshooting: counter resets. See #​10807.

• FEATURE: vmsingle and vmstorage and vmselect in VictoriaMetrics cluster: add the support of ingestion and retrieval of samples with timestamps in the future. The new -futureRetention flag controls how far in the future the timestamps are allowed to be. See #​827 and #​10718.

• FEATURE: dashboards/vmagent, dashboards/cluster: add metadata row ingestion rate queries to related panels. See #​10868.

• BUGFIX: vminsert in VictoriaMetrics cluster: fix increased memory usage after upgrade to v1.140.0 by properly accounting for internal buffer count when calculating per-storage buffer size. See #​10725. Thanks to @​fxrlv for the contribution.

• BUGFIX: all VictoriaMetrics components: properly parse IPv6 source address when accepting connections with proxy protocol v2 enabled. See #​10839. Thanks to @​andriibeee for the contribution.

• BUGFIX: vmagent: properly attach tenant from __tenant_id__ label to the scraped metadata. See #​10828.

• BUGFIX: vmagent: keep tenant ingested into vmagent via prometheus remotewrite endpoint. See #​10828.

• BUGFIX: vmagent and vmsingle: -maxScrapeSize is now correctly applied when reading response bodies, including non-OK scrape error responses. See #​10804.

• BUGFIX: vmagent: fix ec2_sd_configs returning 401 AuthFailure from AWS when credentials are obtained via IRSA, instance role or AWS_CONTAINER_CREDENTIALS_* env vars. The regression was introduced in v1.140.0. See #​10815. Thanks to @​andriibeee for the contribution.

• BUGFIX: vmauth: fix leak of backend TCP connections, file descriptors and goroutines when the client cancels the request after the backend response has been received. See #​10833. Thanks to @​andriibeee for the contribution.

• BUGFIX: vmauth: fix a rare panic during config reload when a backend is marked as broken. See #​10806.

• BUGFIX: vmselect in VictoriaMetrics cluster: stop logging warnings about failed handshakes when the clusternative port receives TCP healthchecks from load balancers. See #​10786. Thanks to @​andriibeee for the contribution.

• BUGFIX: vmrestore: fix an issue where vmrestore could hang indefinitely when interrupted during backup download. See #​10794.

• BUGFIX: vmsingle: properly execute graceful shutdown for vmsingle if -maxIngestionRate is configured. See #​10795.

• BUGFIX: vmui: fix time display on Alerting Rules page to use selected timezone. See #​10827.

• BUGFIX: vmui: use contrasting colors when displaying time series to improve visibility on light and dark themes. See #​10869.

• BUGFIX: vmalert: delete labels from rule results if they are specified with an empty string value in rule or group labels. See #​10766.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: fix incorrect evaluation of binary operations caused by an ordering bug (e.g. 10 - (3 + 3 + 4) being evaluated as 10 - 3 + 3 + 4). The issue was introduced in v1.140.0, v1.136.4, and v1.122.19. See #​10856.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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

---

This PR has been generated by Renovate Bot.

[github-actions]

Here is the diff to main:

--- k8s/infra/observability Kustomization: flux-system/observability HelmRelease: victoriametrics/victoria-metrics

+++ k8s/infra/observability Kustomization: flux-system/observability HelmRelease: victoriametrics/victoria-metrics

@@ -19,7 +19,7 @@

       enabled: true
       image:
         repository: victoriametrics/victoria-metrics
-        tag: v1.140.0
+        tag: v1.141.0
       ingress:
         annotations:
           traefik.ingress.kubernetes.io/router.entrypoints: websecure
--- HelmRelease: victoriametrics/victoria-metrics Service: victoriametrics/victoria-metrics-victoria-metrics-single-server

+++ HelmRelease: victoriametrics/victoria-metrics Service: victoriametrics/victoria-metrics-victoria-metrics-single-server

@@ -8,7 +8,7 @@

     app.kubernetes.io/instance: victoria-metrics
     app.kubernetes.io/managed-by: Helm
     app.kubernetes.io/name: victoria-metrics-single
-    app.kubernetes.io/version: v1.140.0
+    app.kubernetes.io/version: v1.141.0
     helm.sh/chart: victoria-metrics-single-0.35.0
   name: victoria-metrics-victoria-metrics-single-server
 spec:
--- HelmRelease: victoriametrics/victoria-metrics StatefulSet: victoriametrics/victoria-metrics-victoria-metrics-single-server

+++ HelmRelease: victoriametrics/victoria-metrics StatefulSet: victoriametrics/victoria-metrics-victoria-metrics-single-server

@@ -9,7 +9,7 @@

     app.kubernetes.io/instance: victoria-metrics
     app.kubernetes.io/managed-by: Helm
     app.kubernetes.io/name: victoria-metrics-single
-    app.kubernetes.io/version: v1.140.0
+    app.kubernetes.io/version: v1.141.0
     helm.sh/chart: victoria-metrics-single-0.35.0
 spec:
   podManagementPolicy: OrderedReady
@@ -28,7 +28,7 @@

         app.kubernetes.io/instance: victoria-metrics
         app.kubernetes.io/managed-by: Helm
         app.kubernetes.io/name: victoria-metrics-single
-        app.kubernetes.io/version: v1.140.0
+        app.kubernetes.io/version: v1.141.0
         helm.sh/chart: victoria-metrics-single-0.35.0
     spec:
       serviceAccountName: victoria-metrics-victoria-metrics-single-server
@@ -37,7 +37,7 @@

       containers:
       - name: vmsingle
         securityContext: {}
-        image: victoriametrics/victoria-metrics:v1.140.0
+        image: victoriametrics/victoria-metrics:v1.141.0
         imagePullPolicy: IfNotPresent
         args:
         - --envflag.enable
--- HelmRelease: victoriametrics/victoria-metrics Ingress: victoriametrics/victoria-metrics-victoria-metrics-single-server

+++ HelmRelease: victoriametrics/victoria-metrics Ingress: victoriametrics/victoria-metrics-victoria-metrics-single-server

@@ -9,7 +9,7 @@

     app.kubernetes.io/instance: victoria-metrics
     app.kubernetes.io/managed-by: Helm
     app.kubernetes.io/name: victoria-metrics-single
-    app.kubernetes.io/version: v1.140.0
+    app.kubernetes.io/version: v1.141.0
     helm.sh/chart: victoria-metrics-single-0.35.0
   name: victoria-metrics-victoria-metrics-single-server
   namespace: victoriametrics