Skip to content

fix(deps): update module github.com/victoriametrics/operator/api to v0.72.0#612

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-victoriametrics-operator-api-0.x
Open

fix(deps): update module github.com/victoriametrics/operator/api to v0.72.0#612
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-victoriametrics-operator-api-0.x

Conversation

@renovate

@renovate renovate Bot commented May 25, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
github.com/VictoriaMetrics/operator/api v0.66.1 → v0.72.0 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

VictoriaMetrics/operator (github.com/VictoriaMetrics/operator/api)

v0.72.0

Compare Source

Update note 1: vmalert: rule ConfigMaps now store gzip-compressed content in binaryData and an init container decompresses them before VMAlert starts. Existing VMAlert pods will be rolled out once during this upgrade.

  • FEATURE: vmoperator: add validating webhooks for Prometheus Operator CRDs (ServiceMonitor, PodMonitor, PrometheusRule, Probe, ScrapeConfig, AlertmanagerConfig). Each object is converted to its VM equivalent and validated when webhooks are enabled. See #​2270.

  • FEATURE: vmscrapeconfig: add support for consulAgentSDConfigs, dockerSDConfigs, dockerSwarmSDConfigs, marathonSDConfigs, and yandexCloudSDConfigs service discovery types, bringing VMScrapeConfig to full parity with VictoriaMetrics sd_configs. See #​2265.

  • FEATURE: vmalert: rule ConfigMaps now store gzip-compressed rule files in binaryData, allowing larger rule sets within Kubernetes object size limits. An init container decompresses the rules before VMAlert starts.

  • FEATURE: vmscrapeconfig: add support for consulAgentSDConfigs, dockerSDConfigs, dockerSwarmSDConfigs, marathonSDConfigs, and yandexCloudSDConfigs service discovery types, bringing VMScrapeConfig to full parity with VictoriaMetrics sd_configs. See #​2265.

  • FEATURE: vmoperator: add victoriametrics_app=true label to all metrics scraped by the operator. See #​2261.

  • BUGFIX: vmoperator: skip reconciliation only for CRs with genuine spec parse errors; CRs whose ParsingSpecError is caused solely by unknown fields (e.g. after an operator downgrade) are now reconciled normally instead of being silently skipped.

  • BUGFIX: vmoperator: fix potential deadlock in operator_object_status metrics collector when the number of tracked objects exceeds 250. The Collect method previously held a mutex while sending to the prometheus channel, which could deadlock if the channel was full and another goroutine was waiting on the same mutex. See #​2239.

  • BUGFIX: config-reloader: fix missed reload for watched files whose names contain .. (e.g. rules..yaml). Previously any path containing .. was silently skipped; now only Kubernetes synthetic entries whose basename starts with .. (e.g. ..data) are ignored. See #​2253.

  • BUGFIX: vmoperator: fix potential deadlock in operator_object_status metrics collector when the number of tracked objects exceeds 250. The Collect method previously held a mutex while sending to the prometheus channel, which could deadlock if the channel was full and another goroutine was waiting on the same mutex. See #​2239.

v0.71.0

Compare Source

Update note 1: the new default preStop hook causes a rolling update of all applicable pods on operator upgrade (on Kubernetes >= 1.29). To avoid this, set VM_ENABLE_DEFAULT_PRESTOP_HOOK=false on the operator before upgrading. Once the upgrade is complete, you can re-enable it by removing the override (or setting it to true) to roll out the hook at a time of your choosing. Alternatively, disable the hook per resource by setting spec.preStopSleepSeconds: 0.

  • Dependency: vmoperator: Updated default versions for VM apps to v1.145.0 version

  • FEATURE: vmoperator: added VM_COMMON_LABELS and VM_COMMON_ANNOTATIONS environment variables to apply common labels/annotations to all Kubernetes resources managed by the operator. These cannot override labels/annotations already set by the operator or via spec.managedMetadata. This also ensures HTTPRoutes and PVCs include ManagedMetadata labels and annotations

  • FEATURE: vmoperator: support enableServiceLinks property in all CRs. See #​2194.

  • FEATURE: vmalertmanagerconfig: add url_file and alert_source_token_file fields to IncidentioConfig, as file-based alternatives to url and alert_source_token. See #​2222.

  • FEATURE: vmoperator: add status metrics for objects managed by each controller. See #​2238.

  • FEATURE: vmsingle: added spec.downsampling for structured downsampling configuration and spec.retentionFilters for structured retention filters configuration. Both require an enterprise license.

  • FEATURE: vmcluster: added spec.downsampling for structured downsampling configuration (applied to both vmselect and vmstorage) and spec.vmstorage.retentionFilters for structured retention filters configuration. Both require an enterprise license.

  • FEATURE: vmoperator: add default preStop lifecycle hook (15s sleep) to applicable component pods to prevent traffic loss during pod termination. Requires Kubernetes >= 1.29. Storage components (VMStorage, VLStorage, VTStorage) are excluded since their clients handle retries. The sleep duration is configurable via spec.preStopSleepSeconds on any CR; set to 0 to disable. See #​1834.

  • FEATURE: vmanomaly: add missing configuration parameters for vmanomaly config parity: spec.reader.offset and per-query offset, spec.writer.connectionRetryAttempts, spec.server.useReaderConnectionSettings, settings.logger_levels, and the exact/infer_every parameters of the backtesting scheduler. Previously these keys were rejected by strict config parsing.

  • FEATURE: vmcluster: add spec.discovery field with enabled, interval and filter properties to configure automatic vmstorage node discovery for vminsert and vmselect. The field can be set globally or overridden per component via spec.vminsert.discovery and spec.vmselect.discovery. This is an enterprise feature and requires a valid license key. See automatic vmstorage discovery.

  • BUGFIX: vmoperator: update status currentRevision and currentReplicas for StatefulSet with OnDelete update strategy. See #​1242.

  • BUGFIX: config-reloader: fix configreloader_last_reload_success_timestamp_seconds metric to report time in seconds instead of milliseconds.

  • BUGFIX: vmoperator: enable strict CR spec unmarshalling when creating objects. See #​2882.

  • BUGFIX: vmoperator: ignore NotFound errors, that may occur during attempt to update status on a missing resource.

  • BUGFIX: vmagent, vmanomaly: fix VPA scale subresource lookup failure when spec.shardCount is unset by always reporting at least 1 in status.shards. See #​2229.

  • BUGFIX: vmagent: fix HPA targeting the underlying Deployment/StatefulSet (pod replicas) instead of the VMAgent CR scale subresource (spec.shardCount); HPA now correctly scales the number of shards. See #​2229.

  • BUGFIX: vmanomaly: emit the OnlineQuantileModel smoothing parameter under its correct key global_smoothing instead of the unrecognized global_smooth, which vmanomaly silently ignored.

  • BUGFIX: vmanomaly: pass the configured TLS CA bundle to the reader, writer and monitoring clients. Previously the CA was mounted as a volume but dropped during config generation, so a tlsConfig with only a CA produced no verify_tls reference to it; insecureSkipVerify is now also propagated correctly.

  • BUGFIX: vmanomaly: serialize the tz timezone of spec.reader, of each query, and of the periodic scheduler as a string. It was serialized to {} and could not be parsed from a string, so any configuration that set tz failed to reconcile.

  • BUGFIX: vmanomaly: fix the AutoTunedModel trials parameter spelling n_trials, previously it was rendered as n_trails which was silently ignored by vmanomaly.

  • BUGFIX: vmanomaly: preserve an explicit 0.0 for the anomaly_score_outside_data_range parameter (both settings and model level), which was dropped by the underlying float field and silently reverted to the vmanomaly default.

  • BUGFIX: vmanomaly: validate online models' decay against the (0, 1] range while still allowing it to be omitted.

  • BUGFIX: vmanomaly: accept a float value (for example 0.01) for the isolation forest contamination parameter in addition to the string auto.

  • BUGFIX: vmanomaly: omit the OnlineQuantileModel min_subseason key when it is unset instead of emitting an empty string.

  • BUGFIX: vmanomaly: remove the artificial upper bound on spec.server.maxConcurrentTasks; vmanomaly accepts any positive integer.

v0.70.1

Compare Source

  • FEATURE: vmauth: support HPA for requests load balancer.

  • BUGFIX: vmagent: skip replica count update when VMAgent is in stateful mode and HPA is enabled. See #​2190.

  • BUGFIX: vmalertmanagerconfig: Remove prefix from empty subroute receiver. See #​2185.

  • BUGFIX: vmoperator: updated OLM configuration to fix OpenShift catalog publishing. See #​2195.

v0.70.0

Compare Source

v0.69.0

Compare Source

  • Dependency: vmoperator: Updated default versions for VM apps to v1.140.0 version

  • Dependency: vmoperator: Updated default versions for VM apps to v1.139.0 version
    Update note 1: deprecated env variables for Prometheus CRs conversion VM_ENABLEDPROMETHEUSCONVERTER_PODMONITOR, VM_ENABLEDPROMETHEUSCONVERTER_SERVICESCRAPE, VM_ENABLEDPROMETHEUSCONVERTER_PROMETHEUSRULE, VM_ENABLEDPROMETHEUSCONVERTER_PROBE, VM_ENABLEDPROMETHEUSCONVERTER_SCRAPECONFIG. Use -controller.disableReconcileFor command-line flag with comma-separated list of controller names, that should be disabled.
    Update note 2: removed operator_prometheus_converter_watch_events_total metric since migration of Prometheus object watchers to controllers made this counter obsolete.
    Update note 3: made controller.prometheusCRD.resyncPeriod command line flag noop, which was relevant to Prometheus object watchers.
    Update note 4: -eula flag is not set by default anymore for VMBackup and VMRestore. To avoid VMCluster/VMSingle rollouts set spec.vmstorage.vmBackup.acceptEula: true for VMCluster and spec.vmBackup.acceptEula: true" for VMSingle and replace it with spec.license during VMSingle/VMCluster upgrade.
    Update note 5: new flag was introduced, so VMAnomaly pods will be recreated. VMAnomaly version should be at least 1.25.
    Update note 6: fixed port name collision in VMSingle and VMCluster, when VMBackup is enabled. To avoid VMSingle/VMCluster pods recreation set VM_USE_OLD_BACKUP_RESTORE_PORT_NAMES environment variable to true.
    Update note 7: the default VMDistributed unauthorizedUserAccessSpec was removed to allow users to decide whether access should be anonymous or authorized. Please check documentation with examples for unauthorized and authorized access and update your CRs accordingly.

  • Dependency: vmoperator: Updated default versions for VM apps to v1.139.0 version

  • Dependency: vmoperator: Updated default versions for VL apps to v1.50.0.

  • FEATURE: helm-converter: new CLI tool that helps with migration from Helm charts to their corresponding Operator Custom Resources (CRs).

  • FEATURE: vmsingle: VMSingle reuses vmagent implementation to allow scraping and relabelling. See #​1694

  • FEATURE: vmoperator: perform statefulset pods deletion instead of eviction when maxUnavailable set to 100%, which is important for minimum downtime strategy. See #​1706.

  • FEATURE: vmuser: support referencing multiple targets of the same kind at targetRefs[*].crd.objects.

  • FEATURE: vmoperator: prettify reconcile diff in logs, now diff objects show only changed JSON fields.

  • FEATURE: VLCluster, VLSingle, VLAgent, VTCluster, VTSingle, VMCluster, VMAgent, VMAnomaly, VMAlert, VMAlertmanager, VMAuth: add spec.componentVersion as an alternative to spec.clusterVersion. This field also available in all objects deploying pods. See this #​1949 issue for details.

  • FEATURE: vmanomaly: add support for settings.retention configuration (ttl and check_interval) in configRawYaml and configSecret. See these docs for details.

  • FEATURE: vmuser: support JWT-based auth.

  • FEATURE: vmagent: support HPA in VMAgent CR and in VMAgent, which is a part of VMDistributed. See #​1961.

  • FEATURE: vmagent: VMAgent CRs running in statefulSet mode, including VMAgent components in VMDistributed, now support configuring rolling update strategy behavior. See #​1987.

  • FEATURE: vmagent: VMAgent CRs running in DaemonSet mode now support configuring rolling update strategy behavior.

  • FEATURE: vmoperator: Dry-run mode. See #​1832.

  • FEATURE: vmanomaly: introduce VMAnomalyConfig CRD to enable dynamic configuration and hot-reload support starting from VMAnomaly version 1.25.0.

  • FEATURE: vmalertmanager: introduce arbitrary fs access feature for VMAlertmanager. See #​899

  • FEATURE: vmalertmanagerconfig: add update_message field to SlackConfig. This allows alertmanager to edit the original Slack message in-place when alert status changes instead of sending a new one. Requires alertmanager v0.32.0+. See #​2064.

  • BUGFIX: vmbackupmanager: remove deprecated -eula flag from vmbackupmanager and vmrestore container args. See #​1319.

  • BUGFIX: vmoperator: VMPodScrape for VLAgent and VMAgent now uses the correct port; previously it used the wrong port and could cause scrape failures. See #​1887.

  • BUGFIX: vmdistributed: updated VMAuth config consolidating all VMSelects into a single read and all VMClusters into a single write backend

  • BUGFIX: vmdistributed: fix PVC being owned by StatefulSet and top-level object simultaneously. See #​1845.

  • BUGFIX: vmoperator: remove unneeded finalizer from core K8s resources. See #​835.

  • BUGFIX: vmdistributed: remove finalizers from VMServiceScrape and VMPodScrape objects, and keep finalizers on VMAgent, VMCluster, and VMAuth when DeletionTimestamp is not empty.

  • BUGFIX: vmsingle and vmagent: previously, ingest-only mode could still mount scrape configuration secrets when relabeling or stream aggregation was configured, which caused unexpected secret mounts and RBAC-related failures; now these secrets are not mounted in ingest-only mode, so deployments start with the expected minimal permissions and avoid related runtime errors. See #​1828.

  • BUGFIX: vmoperator: recreate STS if immutable fields changed.

  • BUGFIX: vmoperator: wait for STS deletion in case of recreation without throwing an error.

  • BUGFIX: vmdistributed: ignore VMAuth update/delete operations if controller is disabled.

  • BUGFIX: vmalertmanager: fixed ignored tracing config, when no alertmanagerconfig CRs collected. See #​1983.

  • BUGFIX: vmagent: apply scrape class relabellings before job ones. See #​1997.

  • BUGFIX: vmanomaly and vmagent: render %SHARD_NUM% placeholder when shard count is greater than 0. See #​2001.

  • BUGFIX: vlcluster and vtcluster: do not ignore ExtraStorageNodes for select, when default storage is disabled. See #​1910.

  • BUGFIX: vmdistributed: use default stub, when no VMAuth backends are available

  • BUGFIX: vmagent: use volume from spec.volumes as persistent queue volume if its name is persistent-queue-data, previously emptyDir was mounted. See #​1677.

  • BUGFIX: vmcluster: use volume from spec.vmstorage.volumes and spec.vmselect.volumes as data and cache volumes if its name is vmstorage-db and vmselect-cachedir respectively. See #​784.

  • BUGFIX: vmcluster and vmsingle: renamed vmbackup and vmrestore port names, before they had identical to storage/single port names, which is not allowed.

  • BUGFIX: vmsingle: updated scraping implementation to match vmagent functionality.

v0.68.5

Compare Source

Update note: -eula flag is not set by default anymore for VMBackup and VMRestore. To avoid VMCluster/VMSingle rollouts set spec.vmstorage.vmBackup.acceptEula: true for VMCluster and spec.vmBackup.acceptEula: true for VMSingle and replace it with spec.license during VMSingle/VMCluster upgrade.

  • Dependency: vmoperator: Updated default versions for VM apps to v1.144.0 version

  • SECURITY: upgrade Go builder from Go1.25.8 to Go1.25.10. See the list of issues addressed in Go1.25.10.

  • BUGFIX: vmagent: use volume from spec.volumes as persistent queue volume if its name is persistent-queue-data, previously emptyDir was mounted. See #​1677.

  • BUGFIX: vmcluster: use volume from spec.vmstorage.volumes and spec.vmselect.volumes as data and cache volumes if its name is vmstorage-db and vmselect-cachedir respectively. See #​784.

  • BUGFIX: vmoperator: Improve reconcile error handling for Prometheus and VictoriaMetrics controllers.

  • BUGFIX: vmoperator: Add acceptEula support for VMBackup/VMRestore.

  • BUGFIX: vmdistributed: change default load balancing policy for write requests from first_available to least_loaded. This should allow to evenly distribute write load across all VMAgents.

  • BUGFIX: VMCluster, VTCluster and VLCluster: fixed infinite non-default additional service recreation, when requestsLoadBalancer.enabled: true

  • BUGFIX: vmoperator: retry reconcile errors, that may lead to expanding state, before resource could hang in expanding state.

  • BUGFIX: vmdistributed: expose VMClusterSpec parsing error in status, previously it was just swallowed and led to infinite reconciles. See #​2113.

  • BUGFIX: vmanomaly and vmagent: Fix incorrect scaling logs for sharded vmagent and vmanomaly.

v0.68.4

Compare Source

  • FEATURE: vmagent: introduce statefulRollingUpdateStrategyBehavior to allow managing VMAgent update strategy in a statefulMode. See #​1987.

  • FEATURE: vmoperator: Dry-run mode. See #​1832.

  • BUGFIX: vmoperator: wait till PVC resize finished. See #​1970.

  • BUGFIX: vmalertmanager: fixed ignored tracing config, when no alertmanagerconfig CRs collected. See #​1983.

  • BUGFIX: vmagent: apply scrape class relabellings before job ones. See #​1997.

  • BUGFIX: vmanomaly and vmagent: render %SHARD_NUM% placeholder when shard count is greater than 0. See #​2001.

  • BUGFIX: vlcluster and vtcluster: do not ignore ExtraStorageNodes for select, when default storage is disabled. See #​1910.

  • BUGFIX: vmdistributed: use default stub, when no VMAuth backends are available

v0.68.3

Compare Source

  • FEATURE: vmoperator: prettify reconcile diff in logs, now diff objects show only changed JSON fields.

  • FEATURE: vmoperator: introduce VM_LOOPBACK env variable, which allows to override default loopback address, which is either localhost if VM _ENABLETCP6=true or 127.0.0.1 in other cases. Note: this change may cause component rollouts when 127.0.0.1 is used as the loopback address. Make sure to set this env var before upgrading
    .

  • BUGFIX: vmoperator: recreate STS if immutable fields changed.

  • BUGFIX: vmoperator: pod recreation isn't lost after triggerring StatefulSet delete.

  • BUGFIX: vmdistributed: updated VMAuth config consolidating all VMSelects into a single read and all VMAgents into a si
    ngle write backend.

  • BUGFIX: vmoperator: fix finalizer cleanup for VLAgent, VLogs, VMAgent, and VMSingle to target the correct resources.

  • BUGFIX: config-reloader: log-format option supported as fallback for loggerFormat. See [#​1954](https://gi
    thub.com/feat: add log-format as an alias to loggerFormat VictoriaMetrics/operator#1954).

  • SECURITY: upgrade Go builder from Go1.25.7 to Go1.25.8. See the list of issues addressed in Go1.25.8.

v0.68.2

Compare Source

  • Dependency: vmoperator: Updated default versions for VL apps to v1.47.0.

  • BUGFIX: vmoperator: perform statefulset pods deletion instead of eviction when maxUnavailable set to 100%, which is important for minimum downtime strategy. See #​1706.

  • BUGFIX: vmoperator: VMPodScrape for VLAgent and VMAgent now uses the correct port; previously it used the wrong port and could cause scrape failures. See #​1887.

  • BUGFIX: vmdistributed: fix PVC being owned by StatefulSet and top-level object simultaenously. See #​1845.

  • BUGFIX: vmoperator: remove unneeded finalizer from core K8s resources. See #​835.

  • BUGFIX: vmdistributed: remove finalizers from VMServiceScrape and VMPodScrape objects, and keep finalizers on VMAgent, VMCluster, and VMAuth when DeletionTimestamp is not empty.

  • BUGFIX: vmsingle and vmagent: previously, ingest-only mode could still mount scrape configuration secrets when relabeling or stream aggregation was configured, which caused unexpected secret mounts and RBAC-related failures; now these secrets are not mounted in ingest-only mode, so deployments start with the expected minimal permissions and avoid related runtime errors. See #​1828.

  • BUGFIX: vmoperator: do not recreate STS if VCT size was increased and recreate in other cases.

  • BUGFIX: vmoperator: wait for STS deletion in case of recreation without throwing an error.

v0.68.1

Compare Source

SECURITY: upgrade Go builder from Go1.25.5 to Go1.25.7. See the list of issues addressed in Go1.25.7.)

  • BUGFIX: vmanomaly: fix configuration marshalling for Prophet model. Previously, using Prophet model would lead to panic during configuration marshalling.

v0.68.0

Compare Source

Release date: 23 February 2026

Update note 1: deprecated VMProbe's spec.targets.ingress. Use spec.targets.kubernetes slice instead. Please check example of VMProbe with Ingress discovery. This field will be removed in v0.71.0.

Update note 2: deprecated VMProbe's spec.targets.staticConfig. Use spec.targets.static instead. Please check example of VMProbe with static targets. This field will be removed in v0.71.0.

  • Dependency: vmoperator: Updated default versions for VM apps to v1.136.0 version

  • Dependency: vmoperator: Updated default versions for VL apps to v1.45.0.

  • FEATURE: vmalertmanager: added namespace to --cluster.peer arguments explicitly when spec.clusterDomainName is omitted and added unit tests to test this.

  • FEATURE: vmoperator: introduce VMDistributed CR, which helps to propagate changes to each zone without affecting global availability. Before distributed setup deployment was multistep manual action. See #​1515.

  • FEATURE: vlagent: support ability to override default stream fields for vlagent in logs collection mode.

  • FEATURE: vmoperator: added VM_*_EPHEMERAL_STORAGE_REQUEST and VM_*_EPHEMERAL_STORAGE_LIMIT global variables that allow to configure ephemeralStorage requests and limits. See #​1711.

  • FEATURE: vmalertmanager: added tracing support. See #​1770.

  • FEATURE: vmprobe: added spec.targets.kubernetes property, that allows to configure probe for ingress, pod and service roles. See #​1078 and #​1716.

  • FEATURE: vmscrapeconfig: added nomad_sd_config support. See #​1809.

  • FEATURE: vmoperator: support VPA for vmcluster, vtcluster, vlcluster and vmauth. See #​1795. Thanks to the @​dctrwatson for the pull request #​1803.

  • BUGFIX: vmagent: previously the operator requested nodes/proxy RBAC permissions even though vmagent did not use them; now this permission is no longer required, reducing the default privilege footprint for users running vmagent. See #​1753.

  • BUGFIX: vmalert: throw error if no notifiers found. See #​1757.

  • BUGFIX: vlagent: previously the operator emitted quoted spec.k8sCollector.{msgField,timeField,ignoreFields,decolorizeFields} values, which caused vlagent to misparse these fields; now these fields are emitted unquoted so collector settings are applied correctly. See #​1749.

  • BUGFIX: vmoperator: fixed conflicts for VMAlert, VMAlertmanager and VMAuth reconcilers, which are updating same objects concurrently with reconcilers for their child objects.

  • BUGFIX: vmoperator: previously PVC downscaling always emitted a warning, which is not expected, while using PVC autoresizer; now warning during attempt to downsize PVC is only emitted if operator.victoriametrics.com/pvc-allow-volume-expansion: false is not set. See #​1747.

  • BUGFIX: vmoperator: skip self scrape objects management if respective controller is disabled. See #​1718.

  • BUGFIX: vmagent: support both prometheus-compatible endpointslice and old endpointslices roles.

  • BUGFIX: vmanomaly: fix pod metrics port in the default VMPodScrape.

  • BUGFIX: vmoperator: support Prometheus operator AlertmanagerConfig spec.muteTimeIntervals conversion to VMAlertmanagerConfig spec.timeIntervals. See #​1783.

  • BUGFIX: vmoperator: previously StatefulSet/Deployment/DaemonSet rollouts could proceed in parallel, now pods are rolled out sequentially. See #​1693.

  • BUGFIX: config-reloader: previously --only-init-config still kept the reloader running background watchers; now it exits after the initial config update so the pod terminates as expected. See #​1785.

  • BUGFIX: vmoperator: previously, recreating a resource after deletion could hang and block updates; now resource recreation completes normally. See #​1707.

  • BUGFIX: vmoperator: use global image registry unless image.repository is defined. See #​1813.

  • BUGFIX: vmalertmanagerconfig: previously spec.route and spec.receivers were required; now both parameters are optional to align with prometheus operator. VMAlertmanager now can be used to set just the global inhibition rules. See #​1800.

  • BUGFIX: vmoperator: use global image registry unless image.repository is defined. See #​1813.

  • BUGFIX: vmagent: fixed RBAC, when ingestOnlyMode is enabled and relabel of stream aggregation configurations defined. See #​1828.

v0.67.0

Compare Source

Update note 1: removed 3rd-party config reloaders. Now VMAlert, VMAgent, VMAuth and VMAlertmanager are using only VM config reloader. Please verify spec.configReloaderExtraArgs in all instances of VMAlert, VMAuth, VMAgent and VMAlertmanager CRs are using valid config-reloader arguments before upgrading.
Update note 2: removed deprecated VMAgent spec.aPIServerConfig property
Update note 3: removed deprecated VMCluster spec.vmselect.persistentVolume property
Update note 4: VM_CUSTOMCONFIGRELOADERIMAGE is deprecated and will be removed in next releases. Use VM_CONFIG_RELOADER_IMAGE instead.
Update note 5: VMAgent’s, VMAuth’s, VMAlert’s and VMAlertmanager’s spec.configReloaderImageTag is deprecated and will be removed in next releases. Use spec.configReloaderImage instead.
Update note 6: VMAgent’s spec.vmAgentExternalLabelName is deprecated and will be removed in next releases. Use spec.externalLabelName instead.
Update note 7: VMAuth’s spec.unauthorizedUserAccessSpec.url_prefix and spec.unauthorizedUserAccessSpec.url_map are deprecated and will be removed in next releases. Use spec.unauthorizedUserAccessSpec.targetRef instead.
Update note 8: VMServiceScrape’s endpointslices role is deprecated and will be removed in 0.70.0. Use endpointslice instead.

  • Dependency: vmoperator: Updated default versions for VM apps to v1.134.0 version

  • Dependency: vmoperator: Updated default versions for VL apps to v1.43.1.

  • Dependency: vmoperator: Updated default versions for VT apps to v0.7.0 version.

  • Dependency: vmoperator: Updated default versions for VMAnomaly to v1.28.5 version

  • FEATURE: vmagent: support namespace parameter in attach_metadata section for all scrape configurations. See #​1654.

  • FEATURE: vlagent: support logs collection. See #​1501.

  • FEATURE: vmoperator: use operator_bad_objects_total metric with object_namespace and crd labels to track invalid objects managed by VMAgent, VMAuth, VMAlert and VMAlertmanager. Old operator_alertmanager_bad_objects_count and operator_vmalert_bad_objects_count are deprecated and will be removed in next releases.

  • FEATURE: vmoperator: added HPA support for all cluster CR storage. See #​1678.

  • FEATURE: vlagent, vlsingle and vlcluster: support license options. See #​2649.

  • FEATURE: vmanomaly: add support of spec.server configuration.

  • FEATURE: vlagent: add collector extraFilter, includePodLabels, includePodAnnotations, includeNodeLabels and includeNodeAnnotations support for more flexible Kubernetes logs by metadata selection.

  • FEATURE: vlagent: use a single volume for all VLAgent data by default instead of separate volumes/paths for checkpoints and remote write data.

  • FEATURE: vmagent: global sample limit per scrape target is supported via sampleLimit option in scrape config. See #​10168.

  • BUGFIX: vmoperator: fixed HPA cleanup logic for all cluster resources, before it was constantly recreated. Bug introduced in this commit.

  • BUGFIX: VMCluster, VLCluster and VTCluster: prevent cluster load balancer secret from infinite reconcile.

  • BUGFIX: vmsingle, vlsingle and vtsingle: do not mount emptydir if storage data volume is already present in volumes list. Before it was impossible to mount external PVC without overriding default storageDataPath using spec.extraArgs and without having unneeded emptydir listed among pod volumes. Related issues #​1477.

  • BUGFIX: vmoperator: use Service labels instead of selector in VMServiceScrape selector. See #​1709.

  • BUGFIX: vmoperator: update Alertmanager dependency to fix config validation for Incident.io. See #​1730.

  • BUGFIX: vmoperator: do not add -enterprise suffix to image, if tag contains @ symbol. See #​1723.

  • BUGFIX: vmoperator: use 127.0.0.1 instead of localhost in reload and snapshot url for setups without IPV6 enabled.

  • BUGFIX: vmscrapeconfig: properly convert prometheus ScrapeConfig's role into VMScrapeConfig. See #​1735.

  • BUGFIX: [

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • 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 this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented May 25, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 70 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.26.1 -> 1.26.4
github.com/prometheus/prometheus v0.303.1 -> v0.311.3
k8s.io/api v0.35.2 -> v0.36.2
k8s.io/apiextensions-apiserver v0.35.2 -> v0.36.2
github.com/go-openapi/swag/cmdutils v0.24.0 -> v0.26.0
github.com/go-openapi/swag/conv v0.25.5 -> v0.26.0
github.com/go-openapi/swag/fileutils v0.25.5 -> v0.26.0
github.com/go-openapi/swag/jsonname v0.25.5 -> v0.26.0
github.com/go-openapi/swag/jsonutils v0.25.5 -> v0.26.0
github.com/go-openapi/swag/loading v0.25.5 -> v0.26.0
github.com/go-openapi/swag/mangling v0.25.5 -> v0.26.0
github.com/go-openapi/swag/netutils v0.24.0 -> v0.26.0
github.com/go-openapi/swag/stringutils v0.25.5 -> v0.26.0
github.com/go-openapi/swag/typeutils v0.25.5 -> v0.26.0
cel.dev/expr v0.24.0 -> v0.25.1
github.com/VictoriaMetrics/VictoriaLogs v1.36.2-0.20251008164716-21c0fb3de84d -> v1.50.1-0.20260415124154-6b7a6357aec0
github.com/VictoriaMetrics/VictoriaMetrics v1.131.0 -> v1.145.0
github.com/VictoriaMetrics/easyproto v0.1.4 -> v1.2.0
github.com/VictoriaMetrics/metrics v1.40.2 -> v1.43.2
github.com/VictoriaMetrics/metricsql v0.84.8 -> v0.87.1
github.com/bmatcuk/doublestar/v4 v4.9.1 -> v4.10.0
github.com/coreos/go-systemd/v22 v22.5.0 -> v22.7.0
github.com/fsnotify/fsnotify v1.9.0 -> v1.10.0
github.com/fxamacker/cbor/v2 v2.9.0 -> v2.9.2
github.com/go-jose/go-jose/v4 v4.1.3 -> v4.1.4
github.com/go-openapi/analysis v0.24.3 -> v0.25.0
github.com/go-openapi/jsonpointer v0.22.5 -> v0.23.1
github.com/go-openapi/runtime v0.29.3 -> v0.29.4
github.com/go-openapi/strfmt v0.26.0 -> v0.26.2
github.com/go-openapi/swag v0.24.1 -> v0.26.0
github.com/google/gnostic-models v0.7.0 -> v0.7.1
github.com/grpc-ecosystem/grpc-gateway/v2 v2.27.3 -> v2.28.0
github.com/klauspost/compress v1.18.2 -> v1.18.6
github.com/prometheus/alertmanager v0.28.0 -> v0.33.0
github.com/prometheus/procfs v0.17.0 -> v0.20.1
github.com/sirupsen/logrus v1.9.3 -> v1.9.4
github.com/spf13/cobra v1.10.0 -> v1.10.2
github.com/valyala/fastjson v1.6.4 -> v1.6.10
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.63.0 -> v0.68.0
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.64.0 -> v0.68.0
go.opentelemetry.io/otel v1.41.0 -> v1.43.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.39.0 -> v1.43.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.36.0 -> v1.43.0
go.opentelemetry.io/otel/metric v1.41.0 -> v1.43.0
go.opentelemetry.io/otel/sdk v1.41.0 -> v1.43.0
go.opentelemetry.io/otel/trace v1.41.0 -> v1.43.0
go.opentelemetry.io/proto/otlp v1.9.0 -> v1.10.0
go.yaml.in/yaml/v2 v2.4.3 -> v2.4.4
golang.org/x/crypto v0.48.0 -> v0.52.0
golang.org/x/exp v0.0.0-20251002181428-27f1f14c8bb9 -> v0.0.0-20260410095643-746e56fc9e2f
golang.org/x/mod v0.32.0 -> v0.36.0
golang.org/x/net v0.51.0 -> v0.55.0
golang.org/x/oauth2 v0.34.0 -> v0.36.0
golang.org/x/sync v0.19.0 -> v0.20.0
golang.org/x/sys v0.41.0 -> v0.45.0
golang.org/x/term v0.40.0 -> v0.43.0
golang.org/x/text v0.34.0 -> v0.37.0
golang.org/x/time v0.14.0 -> v0.15.0
golang.org/x/tools v0.41.0 -> v0.45.0
google.golang.org/genproto/googleapis/api v0.0.0-20251202230838-ff82c1b0f217 -> v0.0.0-20260414002931-afd174a4e478
google.golang.org/genproto/googleapis/rpc v0.0.0-20251202230838-ff82c1b0f217 -> v0.0.0-20260414002931-afd174a4e478
google.golang.org/grpc v1.78.0 -> v1.80.0
google.golang.org/protobuf v1.36.11 -> v1.36.12-0.20260120151049-f2248ac996af
k8s.io/apimachinery v0.35.2 -> v0.36.2
k8s.io/apiserver v0.35.0 -> v0.36.0
k8s.io/component-base v0.35.0 -> v0.36.1
k8s.io/metrics v0.34.0 -> v0.36.1
k8s.io/utils v0.0.0-20260108192941-914a6e750570 -> v0.0.0-20260507154919-ff6756f316d2
sigs.k8s.io/apiserver-network-proxy/konnectivity-client v0.31.2 -> v0.34.0
sigs.k8s.io/controller-runtime v0.23.3 -> v0.24.1
sigs.k8s.io/structured-merge-diff/v6 v6.3.2 -> v6.4.0

@renovate renovate Bot force-pushed the renovate/github.com-victoriametrics-operator-api-0.x branch from 4864254 to e671595 Compare June 12, 2026 18:36
@renovate renovate Bot changed the title fix(deps): update module github.com/victoriametrics/operator/api to v0.70.1 fix(deps): update module github.com/victoriametrics/operator/api to v0.71.0 Jun 12, 2026
@renovate renovate Bot force-pushed the renovate/github.com-victoriametrics-operator-api-0.x branch from e671595 to 9ca6b76 Compare June 15, 2026 22:02
@renovate renovate Bot changed the title fix(deps): update module github.com/victoriametrics/operator/api to v0.71.0 fix(deps): update module github.com/victoriametrics/operator/api to v0.72.0 Jun 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants