Releases: VictoriaMetrics/operator
Releases · VictoriaMetrics/operator
v0.39.0
v0.39.0 - 4 Oct 2023
Features
- vmoperator: upgrade vmagent/vmauth's default config-reloader image.
- vmuser: adds
retry_status_codes
,max_concurrent_requests
andresponse_headers
settings. It's supported sincev1.94.0
release of vmauth - vmoperator: adds
useStrictSecurity
for all components. It allows to migrate from insecure to strictly secured deployments per component without breaking changes. See this issue for details. - vmoperator: add ability to provide license key for VictoriaMetrics enterprise components. See this doc for the details.
Fixes
- vmcluster: remove redundant annotation
operator.victoriametrics/last-applied-spec
from created workloads like vmstorage statefulset. - vmoperator: properly resize statefulset's multiple pvc when needed and allowable, before they could be updated with wrong size.
- vmoperator: fix wrong api group of endpointsices, before vmagent won't able to access endpointsices resources with default rbac rule.
- vmauth/vmagent: adds default resources for init container with configuration download. See this issue for details.
- vmauth/vmagent: correctly set flag for custom config reloader image during config initialisation. See this issue for details.
- vmauth: correctly set config reloader image for init container.
v0.38.0
v0.38.0
Default version of VictoriaMetrics components: v1.93.4
Fixes
- vmuser: [Enterprise] fixes ip_filters indent for url_prefix. Previously it wasn't possible to use ip_filters with multiple target refs
- vmoperator: turn off
EnableStrictSecurity
by default. Before, upgrade operator to v0.36.0+ could fail components with volume attached, see this issue for details. - vmoperator: bump default version of VictoriaMetrics components to 1.93.4.
Features
- vmoperator add ability to print default values for all operator variables. See this issue for details.
v0.37.1
v0.37.0
VictoriaMetrics Operator v0.37.0
Fixes
- vmagent: fix unmarshalling for streaming aggregation
match
field.
Features
- vmagent: support multiple if conditions for relabeling. See this issue for details.
v0.36.1
v0.36.0
VictoriaMetrics Operator v0.36.0
Breaking changes
-
vmalert: Field
OAuth2
was renamed tooauth2
due to compatibility issue. If you definedOAuth2
with below fields in vmalert objects using operator before v0.36.0, these fields must be reapplied with new tagoauth2
after upgrading. See this issue and this PR for details.- Affected fields:
VMAlert.spec.datasource.OAuth2
->VMAlert.spec.datasource.oauth2
,VMAlert.spec.notifier.OAuth2
->VMAlert.spec.notifier.oauth2
,VMAlert.spec.notifiers[].OAuth2
->VMAlert.spec.notifiers[].oauth2
,VMAlert.spec.remoteRead.OAuth2
->VMAlert.spec.remoteRead.oauth2
,VMAlert.spec.remoteWrite.OAuth2
->VMAlert.spec.remoteWrite.oauth2
,
- Affected fields:
-
vmalert: Field
bearerTokenFilePath
was renamed tobearerTokenFile
due to compatibility issue. If you definedbearerTokenFilePath
with below fields in vmalert objects using operator before v0.36.0, these fields must be reapplied with new tagbearerTokenFile
after upgrading. See this issue and this PR for details.- Affected fields:
VMAlert.spec.datasource.bearerTokenFilePath
-->VMAlert.spec.datasource.bearerTokenFile
,VMAlert.spec.notifier.bearerTokenFilePath
-->VMAlert.spec.notifier.bearerTokenFile
,VMAlert.spec.notifiers[].bearerTokenFile
-->VMAlert.spec.notifiers[].bearerTokenFile
,VMAlert.spec.remoteRead.bearerTokenFilePath
-->VMAlert.spec.remoteRead.bearerTokenFile
,VMAlert.spec.remoteWrite.bearerTokenFilePath
-->VMAlert.spec.remoteWrite.bearerTokenFile
.
- Affected fields:
Fixes
- operator set resource requests for config-reloader container by default. See this PR for details.
- fix
attachMetadata
value miscovert for scrape objects. See this issue and this PR for details. - fix volumeClaimTemplates change check for objects that generate statefulset, like vmstorage, vmselect. Before, the statefulset won't be recreated if additional
claimTemplates
object changed. See this issue and this PR for details. - vmalert: fix
tlsCAFile
argument value generation when using secret or configMap. See this issue and this PR for details. - vmalertmanager: fix default request memory and apply default resources if not set. See this issue and this PR for details.
- vmagent: fix missing additional VolumeClaimTemplates when using
ClaimTemplates
under StatefulMode.
Features
- vmagent: add example config for vmagent statefulmode.
- vmagent/vmsingle: adapt new features in streaming aggregation:
- support
streamAggr.dropInput
, see this issue for details; - support list for
match
parameter, see this issue for details; - support
staleness_interval
, see this issue for details.
- support
- vmcluster: add example config for cluster with custom storage claims.
- vmrule: support
update_entries_limit
field in rules, refer to alerting rules. See this PR for details. - vmrule: support
keep_firing_for
field in rules, refer to alerting rules. See this PR for details. - vmoperator parameters: Add option
VM_ENABLESTRICTSECURITY
and enable strict security context by default. See this issue, this and this PR for details. - vmoperator parameters: change option
VM_PSPAUTOCREATEENABLED
default value fromtrue
tofalse
cause PodSecurityPolicy already got deprecated since kubernetes v1.25. See this pr for details.
v0.35.1
v0.35.0
Changes since v0.34.0
Fixes
- vmuser: fix vmselect url_map in vmuser. See this issue for details. Thanks @Haleygo
- vmalert: correctly set default port for vmauth components discovery. See this issue for details. Thanks @Haleygo
- vmuser: remove rate limit on delete. In #672. Thanks @Haleygo
- vmcluster: fix spec change check. See this issue for details. Thanks @Haleygo
- Corretly publish multi-arch release at #681. Thanks @Haleygo
Feautres
- vmagent:add validation when generate static scrape config. See this issue for details. Thanks @Haleygo
- vmalertmanagerconfig : add validation for slack receiver url. See this issue for details. Thanks @Haleygo
- vmauth/vmagent: implement configuration initiation for custom config reloader. See this issue for details. Thanks @Haleygo
- add more generators Thanks @Haleygo in #668
- vmsingle: add status field. See this issue for details. Thanks @Haleygo
Full Changelog: v0.34.1...v0.35.0
v0.34.1
Changes since v0.34.0
Fixes
- [VMCluster] - fail fast on misconfigured or missing kubernetes pods. It should prevent rare bug with cascade pod deletion. See this issue for details
- [VMAuth/VMAgent]- correctly renders initConfig image with global container registry domain. See this issue for details.
- [VMAgent] - correctly set RBAC permissions for single namespace mode and custom config reloader image. See this issue for details.
v0.34.0
Changes since v0.33.0
Breaking changes
- [Operator]: allows to properly run operator with single namespace. It changes default behavior with WATCH_NAMESPACE param is set. Operator will no longer make any calls for cluster wide resources and create only single namespace config for
VMAgent
. #641
Fixes
- [VMNodeScrape]: fixed selectors for Exists and NotExists operators with empty label Thanks @Amper in #646
- [VMRule] Add config for vmrule in validating webhook Thanks in #650
- [VMAgent]: skips misconfigured objects with missed secret references: #648
- [VMAgent]: correctly renders initContainer for configuration download: #649
Features
- [VMAlertmanager]: Bump alertmanager to v0.25.0 Thanks @tamcore in #636
- [VMCluster] added
clusterNativePort
field to VMSelect/VMInsert for multi-level cluster setup (#634) Thanks @Amper in #639 - [VMRule]: add notifierHeader field in vmrule spec Thanks @Haleygo in #622
- [VMPodScrape]: adds FilterRunning option as prometheus does in #640
- [VMAuth]: adds latest features in #642
Full Changelog: v0.33.0...v0.34.0