VictoriaMetrics/operator v0.55.0

on GitHub

v0.55.0

Release date: 02 Apr 2025

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

• Dependency: vmoperator: make project layout compatible with [kubebuilder v4](https://book.kubebuilder.io/migration/v3vsv4)

• Dependency: vmoperator: Updated default VLogs v1.17.0 version

• FEATURE: [operator](https://docs.victoriametrics.com/operator: add tls_config and proxy_url fields to the oauth2 scrape target configurations. See this issue for details

• FEATURE: [operator](https://docs.victoriametrics.com/operator: add extraEnvsFrom field to all applications, which defines source for env variables as Secret or ConfigMap. See this issue for details.

• FEATURE: [operator](https://docs.victoriametrics.com/operator: set publishNotReadyAddresses: true to the vmstorage, vmselect, vmalertmanager services. See this issue for details.

• FEATURE: [operator](https://docs.victoriametrics.com/operator: log fields changes diff for Deployment, StatefulSet, Service, PDB, HPA and VMServiceScrape during reconcile process. See this issue for details.

• FEATURE: [operator](https://docs.victoriametrics.com/operator: add global env variables VM_CONFIG_RELOADER_LIMIT_CPU and VM_CONFIG_RELOADER_LIMIT_MEMORY with unlimited as default value. It controls global limits for config-reloader containers. See this issue for details.

• FEATURE: [operator](https://docs.victoriametrics.com/operator: add global env variables VM_CONFIG_RELOADER_REQUEST_CPU and VM_CONFIG_RELOADER_REQUEST_MEMORY with empty as default value. It controls global requests for config-reloader containers. See this issue for details. All per resource config-reloader requests env variables are now deprecated.

• FEATURE: vmagent: introduce daemonSetMode as a beta feature. See this issue and this docs for details.

• FEATURE: vmagent: reduce Kubernetes API server load on large scale by removing selectors from VMPodscrape kubernetes_sd_configs. Add new field VMAgent.spec.enableKubernetesAPISelectors, which restores original behaviour. See this issue for details.

• FEATURE: vmagent: allow to define remoteWrite.MaxDiskUsage as integer and adds validation to it. See this issue for details.

• FEATURE: vmagent: allow to define remoteWriteSettings.maxDiskUsagePerURL as string with bytes suffix and adds validation to it. See this issue for details.

• FEATURE: vmalertmanagerconfig: add content, username and avatar_url to discord_configs definition. It's supported by alertmanager v0.28.0+. See this commit for details.

• FEATURE: vmalertmanagerconfig: add new receiver jira_configs, which was added at alertmanager v0.28.0. See this issue for details.

• FEATURE: vmalertmanagerconfig: add new receiver rocketchat_configs, which was added at alertmanager v0.28.0. See this issue for details.

• FEATURE: vmalertmanagerconfig: add new receiver msteamsv2_configs, which was added at alertmanager v0.28.0. See this issue for details.

• BUGFIX: operator: properly throttle concurrent reconcile events on high load. By raising default value for the controller.maxConcurrentReconciles command-line flag from 5 to 15. See this issue for details.

• BUGFIX: vmoperator: properly track immutable fields changes for StatefulSet. See this issue for details.

• BUGFIX: vmcluster: properly propagate podMetadata to requestsLoadBalancer Deployment. See this PR for details. Thanks to the @solidDoWant

• BUGFIX: vmauth: properly sort VMUsers at generated configuration. See this issue for details.

• BUGFIX: vmprobe: properly add vmProberSpec.scheme to the generated configuration. See this issue for details.

• BUGFIX: vmagent: properly apply remoteWriteSettings.maxDiskUsagePerURL global setting. Previously, if remoteWrite.MaxDiskUsage was set to 1 remoteWrite and others don't have this setting, default value was used instead of remoteWriteSettings. See this issue for details.