-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update dependency victoriametrics/operator to v0.51.2 #411
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/victoriametrics-operator-0.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.39.4
chore(deps): update dependency victoriametrics/operator to v0.40.0
Jan 24, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
January 24, 2024 12:36
2d1cb9a
to
2914bf4
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.40.0
chore(deps): update dependency victoriametrics/operator to v0.40.0 - autoclosed
Jan 25, 2024
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.40.0 - autoclosed
chore(deps): update dependency victoriametrics/operator to v0.40.0
Jan 31, 2024
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.40.0
chore(deps): update dependency victoriametrics/operator to v0.41.0
Jan 31, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
January 31, 2024 01:22
2914bf4
to
a38310e
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.41.0
chore(deps): update dependency victoriametrics/operator to v0.41.1
Feb 1, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
February 1, 2024 23:58
a38310e
to
be42126
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.41.1
chore(deps): update dependency victoriametrics/operator to v0.41.2
Feb 21, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
February 21, 2024 13:36
be42126
to
b28f9a7
Compare
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
March 4, 2024 19:32
b28f9a7
to
65a5694
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.41.2
chore(deps): update dependency victoriametrics/operator to v0.42.0
Mar 4, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
March 5, 2024 15:42
65a5694
to
6bca76b
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.42.0
chore(deps): update dependency victoriametrics/operator to v0.42.1
Mar 5, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
March 6, 2024 01:38
6bca76b
to
ab4c03c
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.42.1
chore(deps): update dependency victoriametrics/operator to v0.42.2
Mar 6, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
March 12, 2024 13:27
ab4c03c
to
e9291b8
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.42.2
chore(deps): update dependency victoriametrics/operator to v0.42.3
Mar 12, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
April 2, 2024 18:53
e9291b8
to
c9336d1
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.42.3
chore(deps): update dependency victoriametrics/operator to v0.42.4
Apr 2, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
April 2, 2024 23:38
c9336d1
to
b88c6fe
Compare
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
April 18, 2024 12:18
b88c6fe
to
ea40519
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.42.4
chore(deps): update dependency victoriametrics/operator to v0.43.0
Apr 18, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
April 18, 2024 19:47
ea40519
to
2ad5ff3
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.43.0
chore(deps): update dependency victoriametrics/operator to v0.43.1
Apr 18, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
April 22, 2024 14:24
2ad5ff3
to
e3efe32
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.46.4
chore(deps): update dependency victoriametrics/operator to v0.47.0
Aug 15, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
August 23, 2024 10:21
1976c76
to
807f1c5
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.47.0
chore(deps): update dependency victoriametrics/operator to v0.47.1
Aug 23, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
August 26, 2024 16:30
807f1c5
to
7154478
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.47.1
chore(deps): update dependency victoriametrics/operator to v0.47.2
Aug 26, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
August 30, 2024 00:05
7154478
to
0a62ca2
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.47.2
chore(deps): update dependency victoriametrics/operator to v0.47.3
Aug 30, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
September 25, 2024 23:14
0a62ca2
to
d69b6dd
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.47.3
chore(deps): update dependency victoriametrics/operator to v0.48.0
Sep 25, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
September 26, 2024 16:47
d69b6dd
to
36498dc
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.48.0
chore(deps): update dependency victoriametrics/operator to v0.48.1
Sep 26, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
September 27, 2024 19:51
36498dc
to
abba0a1
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.48.1
chore(deps): update dependency victoriametrics/operator to v0.48.2
Sep 27, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
September 29, 2024 21:40
abba0a1
to
ce87d6a
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.48.2
chore(deps): update dependency victoriametrics/operator to v0.48.3
Sep 29, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
October 15, 2024 14:44
ce87d6a
to
e310f79
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.48.3
chore(deps): update dependency victoriametrics/operator to v0.48.4
Oct 15, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
November 5, 2024 19:59
e310f79
to
82ae251
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.48.4
chore(deps): update dependency victoriametrics/operator to v0.49.0
Nov 5, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
November 11, 2024 14:12
82ae251
to
c5c493e
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.49.0
chore(deps): update dependency victoriametrics/operator to v0.49.1
Nov 11, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
November 25, 2024 09:45
c5c493e
to
fd742b6
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.49.1
chore(deps): update dependency victoriametrics/operator to v0.50.0
Nov 25, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
December 19, 2024 13:10
fd742b6
to
02bb1d8
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.50.0
chore(deps): update dependency victoriametrics/operator to v0.51.0
Dec 19, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
December 19, 2024 15:46
02bb1d8
to
403a287
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.51.0
chore(deps): update dependency victoriametrics/operator to v0.51.1
Dec 19, 2024
renovate
bot
force-pushed
the
renovate/victoriametrics-operator-0.x
branch
from
December 23, 2024 20:46
403a287
to
595dcf8
Compare
renovate
bot
changed the title
chore(deps): update dependency victoriametrics/operator to v0.51.1
chore(deps): update dependency victoriametrics/operator to v0.51.2
Dec 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.42.3
->0.51.2
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
VictoriaMetrics/operator (VictoriaMetrics/operator)
v0.51.2
Compare Source
v0.51.2
Release date: 23 Dec 2024
SECURITY: upgrade Go builder from Go1.23 to Go1.23.4. See the list of issues addressed in Go1.23.2 and Go1.23.3.
BUGFIX: vmoperator: keep
resourceVersion
and other significantmetadata
fields duringupdate
objects requests. See this issue for details.BUGFIX: vmoperator: properly update
updateStatus: failed
field. It fixes excessive errors logging and amount of created KubernetesEvents
.BUGFIX: vmoperator: Properly rollback incorrect object configuration. Previously diff for objects could be calculate incorrectly and update request could be skipped.
BUGFIX: vmcluster and vmsingle: restore deprecated fields
status.clusterStatus
andstatus.singleStatus
removed atv0.51.0
. Those deprecated fields will be removed at upcomingv0.52.0
version.v0.51.1
Compare Source
v0.51.1
Release date: 19 Dec 2024
Update note 1:
labels
andannotations
inheritance is deprecated and will be remove at upcomingv0.52.0
release. It's recommend to move all needed labels and annotations to thespec.managedMetadata
fields.Operator will preserve
annotations
, but any changes to it will be ignored.labels
inherited fromCRD.metata.labels
will be removed after upgrade tov0.52.0
.Update note 2:
VMAuth.spec.unauthorizedAccessConfig
is deprecated in favour ofVMAuth.spec.unauthorizedUserAccessSpec
. Operator still serves deprecated fields untilv1.0
release.Update note 3: The following fields:
[default_url,tlsConfig,discover_backend_ips,headers,response_headers,retry_status_codes,max_concurrent_requests,load_balancing_policy,drop_src_path_prefix_parts]
are deprecated atVMAuth.spec.
in favour ofVMAuth.spec.unauthorizedUserAccessSpec
. Operator still serves deprecated fields untilv1.0
release."app.kubernetes.io/part-of": "vmcluster"
label to the objects generated forVMCluster
components. It helps to use labels selectors to identify objects belong to the cluster.spec
settingunauthorizedUserAccessSpec
that replacesunauthorizedAccessConfig
and inlined fields fromVMUserConfigOptions
. See this issue for details.src_headers
,src_query_args
anddiscover_backend_ips
in the generate vmauth config when specified undervmuserSpec.targetRefs
.dump_request_on_errors
tovmuser.spec
. See this PR for details.annotations
to thePodDisruptionBudget
andHorizontalPodAutoscaler
objects generated.vmagentSpec.ScrapeConfigSelector
andvmagentSpec.scrapeConfigNamespaceSelector
whenvmagentSpec.selectAllByDefault=false
. Previously, the VMScrapeConfig could be ignored.xxxNamespaceSelector
whenvmagentSpec.selectAllByDefault=true
. See this doc for detailed rules.license.forceOffile
andlicense.reloadInterval
options. See this doc for the details.securityContext
to thecontainers
withuseStrictSecurity: false
. See this issue for details.containers
with enableduseStrictSecurity: true
. It setsprivileged: false
.msg
body, changelogger
field to properly displaycontroller.CRD
name. See this issue for details.managedMetadata
toVMCluster.spec
,VMAgent.spec
,VMAlert.spec
,VMAuth.spec
,VMAlertmanager.Spec
,VMSingle.spec
andVLogs.spec
. It controlslabels
andannotations
added to the objects created operator (such asDeployment
). See this issue for details.replace
directive fromgo.mod
.status
sub-resource forVMUser
,VMAlertmanager
,VMRule
andVMScrape.*
objects. Add newconditions
field, that represents resources conditions. See this issue for details.v0.51.0
Compare Source
v0.51.0
Release date: 19 Dec 2024
Update note 1:
labels
andannotations
inheritance is deprecated and will be remove at upcomingv0.52.0
release. It's recommend to move all needed labels and annotations to thespec.managedMetadata
fields.Operator will preserve
annotations
, but any changes to it will be ignored.labels
inherited fromCRD.metata.labels
will be removed after upgrade tov0.52.0
.Update note 2:
VMAuth.spec.unauthorizedAccessConfig
is deprecated in favour ofVMAuth.spec.unauthorizedUserAccessSpec
. Operator still serves deprecated fields untilv1.0
release.Update note 3: The following fields:
[default_url,tlsConfig,discover_backend_ips,headers,response_headers,retry_status_codes,max_concurrent_requests,load_balancing_policy,drop_src_path_prefix_parts]
are deprecated atVMAuth.spec.
in favour ofVMAuth.spec.unauthorizedUserAccessSpec
. Operator still serves deprecated fields untilv1.0
release."app.kubernetes.io/part-of": "vmcluster"
label to the objects generated forVMCluster
components. It helps to use labels selectors to identify objects belong to the cluster.spec
settingunauthorizedUserAccessSpec
that replacesunauthorizedAccessConfig
and inlined fields fromVMUserConfigOptions
. See this issue for details.src_headers
,src_query_args
anddiscover_backend_ips
in the generate vmauth config when specified undervmuserSpec.targetRefs
.dump_request_on_errors
tovmuser.spec
. See this PR for details.annotations
to thePodDisruptionBudget
andHorizontalPodAutoscaler
objects generated.vmagentSpec.ScrapeConfigSelector
andvmagentSpec.scrapeConfigNamespaceSelector
whenvmagentSpec.selectAllByDefault=false
. Previously, the VMScrapeConfig could be ignored.xxxNamespaceSelector
whenvmagentSpec.selectAllByDefault=true
. See this doc for detailed rules.license.forceOffile
andlicense.reloadInterval
options. See this doc for the details.securityContext
to thecontainers
withuseStrictSecurity: false
. See this issue for details.containers
with enableduseStrictSecurity: true
. It setsprivileged: false
.msg
body, changelogger
field to properly displaycontroller.CRD
name. See this issue for details.managedMetadata
toVMCluster.spec
,VMAgent.spec
,VMAlert.spec
,VMAuth.spec
,VMAlertmanager.Spec
,VMSingle.spec
andVLogs.spec
. It controlslabels
andannotations
added to the objects created operator (such asDeployment
). See this issue for details.replace
directive fromgo.mod
.status
sub-resource forVMUser
,VMAlertmanager
,VMRule
andVMScrape.*
objects. Add newconditions
field, that represents resources conditions. See this issue for details.v0.50.0
Compare Source
v0.50.0 - 22 Nov 2024
container
labels to the metrics discovered withVMServiceScrape
forendpointslices
discovery role.VM_VMSERVICESCRAPEDEFAULT_ENFORCEENDPOINTSLICES
to useendpointslices
instead ofendpoints
as discovery role for VMServiceScrape when generate scrape config for VMAgent.loggerJSONFields
to the operator logger configuration. It allows to change json encoder fields. See this issue for details.observedGeneration
. See this issue for details.updateStatus
field for CRD objects. It replacesstatus
,clusterStatus
andsingleStatus
forVLogs
,VMCluster
andVMSingle
with genericupdateStatus
.v0.49.1
Compare Source
v0.49.1 - 11 Nov 2024
type
.VMScrapeConfig
during operator start-up.operational
update status for CRDs. Previously,operational
status could be set before rollout finishes at Kubernetes due to bug at Kubernetescontroller-manager
.New Contributors
Full Changelog: VictoriaMetrics/operator@v0.49.0...v0.49.1
v0.49.0
Compare Source
v0.49.0 - 05 Nov 2024
useStrictSecurity: true
to theinitContainers
forVMAuth
,VMAgent
andVMAlertmanager
. See this issue for details.spec.configSecret
tospec.externalConfig.secretRef.name
and addedspec.externalConfig.localPath
to be able to provide custom configs via sidecar.requestsLoadBalancer
configuration to theVMCluster.spec
. See this issue for details.VMCluster
with enabledbackup
.ConfigMap
provided via.spec.configMap
are changed.v0.48.4
Compare Source
v0.48.4 - 15 Oct 2024
maxDiskUsagePerUrl
andforceVMProto
to theVMagent
remoteWriteSpec
statefulMode
. See this issue for details.OwnerRefrence
forRole
andRoleBinding
atsingle-namespace
operator mode.useStrictSecurity
enabled by removing default values forAppArmorProfile
andSeccompProfile
. See this issue for details.New Contributors
Full Changelog: VictoriaMetrics/operator@v0.48.3...v0.48.4
v0.48.3
Compare Source
v0.48.3 - 29 Sep 2024
VMCluster
sincev0.48.0
release. See this issue for details.--disableControllerForCRD
. It allows to disable reconcile controller for the given comma-separated list of CRD names. See this issue for details.v0.48.2
Compare Source
v0.48.2 - 27 Sep 2024
vm_app_version
metric tag withversion
andshort_version
build info. It was broken since v0.46.0 release.controller.maxConcurrentReconciles
from1
to5
. It should improve reconcile performance for the most installations.rest_client_request_duration_seconds
,sched_latencies_seconds
. It allows to better debug operator reconcile latencies.v0.48.1
Compare Source
v0.48.1 - 26 Sep 2024
updating service
log messages.imagePullSecrets
to the components. Due to bug at0.48.0
operator ignoredvmcluster.spec.imagePullSecrets
See this issue for details.v0.48.0
Compare Source
v0.48.0 - 25 Sep 2024
useVMConfigReloader
,configReloaderImageTag
,configReloaderResources
to theVMagent
,VMAlert
,VMAuth
, andVMAlertmanager
.enforcedTopRouteMatchers
. It adds given alert label matchers to the top route of anyVMAlertmanagerConfig
. See this issue for details.host_aliases
setting, which has priority overhostAliases
.useDefaultResources
setting to the all applications. It has priority over global operator setting.clusterDomainName
to theVMCluster
andVMAlertmanager
. It defines optional suffix for in-cluster addresses.disableSelfServiceScrape
setting to the all applications. It has priority over global operator setting.securityContext
and apply security configuration parameters to the containers.VM_DEFAULTLABELS
,VM_PODWAITREADYINITDELAY
. Adds new variableVM_APPREADYTIMEOUT
.hostAliases
fields to spec. See this issue for details.secrets
andconfigmaps
. Adds new flag-controller.disableCacheFor=seccret,configmap
to disable it if needed.Secret
andConfigmap
values by default. This behaviour could be changed with flagdisableSecretKeySpaceTrim
. Related issue.New Contributors
Full Changelog: VictoriaMetrics/operator@v0.47.3...v0.48.0
v0.47.3
Compare Source
v0.47.3 - 28 Aug 2024
v0.47.2
Compare Source
v0.47.2 - 26 Aug 2024
spec.Port
. See this PR for details.rollingUpdate
strategyType readiness check.crd.kind
enum param forVMAlertmanager
, it now supports bothVMAlertmanager
andVMAlertManager
. See this issue for details.configReloaderExtraArgs
.v0.47.1
Compare Source
v0.47.1 - 23 Aug 2024
It is recommended upgrading to operator v0.47.2 because v0.47.1 contains a bug, which can lead to endless statefulset reconcile loop.
revisionHistoryLimitCount
change. See this issue for details.tls_config
foremails
notifications. See this issue for details.reload
prefix to all config-reloadertls*
flags to avoid collision with flags from external package. See this issuev0.47.0
Compare Source
v0.47.0 - 15 Aug 2024
Breaking changes
Update note 1: operator now forbids cross VMAlertmanagerConfig or global receiver references. VMAlertmanagerConfig must include only local receivers .
Update note 2: removed deprecated
mute_time_intervals
fromVMAlertmanagerConfig.spec
. UseVMAlertmanagerConfig.spec.time_intervals
instead.Update note 3: operator adds
blackhole
as default route forVMalertmanager
if root route receiver is empty. Previously it added a first VMAlertmanagerConfig receiver. Update global VMalertmanager configuration with proper route receiver if neededvictoria-logs: added
VLogs
resource for VictoriaLogs management. Related issue.config-reloader: adds new flags
tlsCaFile
,tlsCertFile
,tlsKeyFile
,tlsServerName
,tlsInsecureSkipVerify
. It allows to configuretls
for reload endpoint. Related issue.vmuser: adds
status.lastSyncError
field, adds server-side validation forspec.targetRefs.crd.kind
. Adds small refactoring.vmuser: allows to skip
VMUser
fromVMAuth
config generation if it has misconfigured fields. Such as references to non-existCRD
objects or missing fields. It's highly recommended to enableValidation
webhook forVMUsers
, it should reduce surface of potential misconfiguration. See this issue for details.vmagent: adds
status
andlastSyncError
status fields to all scrape objects -VMServiceScrape
,VMPodScrape
,VMNodeScrape
,VMPodScrape
,VMStaticScrape
andVMScrapeConfig
. It allows to track config generation forvmagent
from scrape objects.operator: refactors config builder for
VMAgent
. It fixes minor bug with incorrect skip of scrape object with incorrect references for secrets and configmaps.operator: allows to secure
metrics-bind-address
webserver withTLS
andmTLS
protection via flagstls.enable
,tls.certDir
,tls.certName
,tls.key``,
mtls.enable,
mtls.clietCA`. See this issue for details.operator: fixes bug with possible
tlsConfig
SecretOrConfigmap
references clash. Operator addsconfigmap
prefix to the configmap refrenced tls asset. See this issue for details.operator: properly release
PodDisruptionBudget
object finalizer. Previously it could be kept due to typo. See this issue for details.operator: refactors finalizers usage. Simplifies finalizer manipulation with helper functions
operator: adds
tls_config
andauthKey
settings to auto-createdVMServiceScrape
for CRD objects fromextraArgs
. See this issue for details.vmalertmanagerconfig: Improves config validation. Now it properly tracks required fields and provides better feedback for misconfiguration. Adds new
status
fields -status
andlastSyncError
. Related issue.vmalertmanager: adds
webConfig
that simplifies tls configuration for alertmanager and allows to properly build probes and access urls for alertmanager. See this issue for details.vmalertmanager: adds
gossipConfig
to setup client and server TLS configuration for alertmanager.vmagent/vmsingle: sync stream aggregation options
dropInputLabels
,ignoreFirstIntervals
,ignoreOldSamples
from upstream, and support using configMap as the source of aggregation rules.operator: added
-client.qps
and-client.burst
flags to override default QPS and burst K8S params. Related issue.v0.46.4
Compare Source
v0.46.4 - 9 Jul 2024
Breaking changes
Update note 1: for operatorhub based
VMAgent
deploymentserviceAccount
vmagent
must be removed. It's no longer shipped with bundle. After deletion operator will create new account with needed permissions.[manifests]: properly add webhook.enable for operatorhub deployments. See this commit
7a460b0
for details.[manifests]: removes exact user from
runAsUser
setting. It must be defined atdocker image
orsecurity profile
level. See this commit1cc4a0e
for details. by @AndrewChubatiukoperator: switches from distroless to scratch base image. See this commit
768bf76
for details. by @AndrewChubatiukconfig-reloader: do not specify
command
for container.command
configured atdocker image
level. See this commit2192115
for details. by @AndrewChubatiuk[build-scripts]: fixed replaced version extraction by @AndrewChubatiuk in https://github.com/VictoriaMetrics/operator/pull/1026
Full Changelog: VictoriaMetrics/operator@v0.46.3...v0.46.4
v0.46.3
Compare Source
v0.46.3 - 5 Jul 2024
config-reloader
image tag name after 0.46.0 release. See this issue for details.PodMonitor
convertion with configuredtlsConfig
. See this issue for details.targetPort
forVMPodScrape
definition. See this issue for details.Full Changelog: VictoriaMetrics/operator@v0.46.2...v0.46.3
v0.46.2
Compare Source
v0.46.2 - 4 Jul 2024
Updates
targetPort
forVMPodScrape
definition. See this issue for details.Full Changelog: VictoriaMetrics/operator@v0.46.0...v0.46.2
v0.46.1
Compare Source
v0.46.1 - 3 Jul 2024
Breaking changes
--metrics-addr
command-line flag atoperator
was deprecated. Use--metrics-bind-address
instead.--enable-leader-election
command-line flag atoperator
was deprecated. Use--leader-elect
instead.--http.readyListenAddr
command-line flag atoperator
was deprecated. Use--health-probe-bind-address
instead./insert/multitenant/<suffix>
needs to be added inremoteWrite.url
if storage supports multitenancy when usingremoteWriteSettings.useMultiTenantMode
, as upstream vmagent has deprecated-remoteWrite.multitenantURL
command-line flag since v1.102.0.Updates
tls
flag check forAsURL
method. It must allow to usehttps
configuration forVMUser
service discovery. See this issue for details.handleReconcileErr
callback to the reconcile loop. It must properly handle errors and deregister objects.eval_offset
,eval_delay
andeval_alignment
from upstream.xxNamespaceSelector
andxxSelector
options, previously they are inverted. See this issue for details.series_limit
andsample_limit
fields in generated scrape_config. See this issue.v0.46.0
Compare Source
v0.46.0 - 3 Jul 2024
Breaking changes
--metrics-addr
command-line flag atoperator
was deprecated. Use--metrics-bind-address
instead.--enable-leader-election
command-line flag atoperator
was deprecated. Use--leader-elect
instead.--http.readyListenAddr
command-line flag atoperator
was deprecated. Use--health-probe-bind-address
instead./insert/multitenant/<suffix>
needs to be added inremoteWrite.url
if storage supports multitenancy when usingremoteWriteSettings.useMultiTenantMode
, as upstream vmagent has deprecated-remoteWrite.multitenantURL
command-line flag since v1.102.0.Updates
tls
flag check forAsURL
method. It must allow to usehttps
configuration forVMUser
service discovery. See this issue for details.handleReconcileErr
callback to the reconcile loop. It must properly handle errors and deregister objects.eval_offset
,eval_delay
andeval_alignment
from upstream.xxNamespaceSelector
andxxSelector
options, previously they are inverted. See this issue for details.series_limit
andsample_limit
fields in generated scrape_config. See this issue.v0.45.0
Compare Source
v0.45.0 - 10 Jun 2024
cr.spec.configSecret
if it's name clashes with secret used by operator for storing alertmanager config. See this issue for details.DeletetionTimestamp
. See this issue for details.opsgenie_configs
. See this issue.v0.44.0
Compare Source
v0.44.0 - 9 May 2024
streamAggrConfig
:dedup_interval
,ignore_old_samples
,keep_metric_names
,no_align_flush_to_interval
. It's only possible to use it with v1.100+ version ofvmagent
. See this issue for details.Patch
forfinalizers
set/unset operations. It must fix possible issues withCRD
objects mutations. See this issue for details.spec.pause
field toVMAgent
,VMAlert
,VMAuth
,VMCluster
,VMAlertmanager
andVMSingle
. It allows to suspend object reconcile by operator. See this issue for details. Thanks @just1900status.selector
field. It allows correctly useVPA
withvmagent
. See this issue for details.spec
field for it. See this issue for details.authorization
section in sd configs works properly with emptytype
field (default value for this field isBearer
).v0.43.5
Compare Source
What's Changed
Full Changelog: VictoriaMetrics/operator@v0.43.4...v0.43.5
v0.43.4
Compare Source
v0.43.4 - 25 Apr 2024
expanding
forVMCluster
during initial creation. Previously, it was alwaysoperational
.Deployment
andStatefulset
watch ready functions. Now, it reports state of unhealthy pod. It allows to find issue with it faster.v0.43.3
Compare Source
v0.43.3 - 23 Apr 2024
ServiceMonitor
toVMServiceScrape
,bearerTokenSecret
is dropped mistakenly since v0.43.0. See this issue.v0.43.2
Compare Source
v0.43.2 - 22 Apr 2024
ServiceAccount
not found withingestOnlyMode
.unknown long flag '--rules-dir'
for prometheus-config-reloader.v0.43.1
Compare Source
Full Changelog: VictoriaMetrics/operator@v0.43.0...v0.43.1
v0.43.0
Compare Source
v0.43. - 18 Apr 2024
Update note: vmcluster: remove fields
VMClusterSpec.VMInsert.Name
,VMClusterSpec.VMStorage.Name
,VMClusterSpec.VMSelect.Name
, they're marked as deprecated since v0.21.0. See this pull request.Update note: PodSecurityPolicy supports was deleted. Operator no long creates PSP related objects since it's no longer supported by Kubernetes actual versions. See this doc for details.
Update note: PodDisruptionBudget at betav1 API is no longer supported. Operator uses v1 stable version. See this doc for details.
Update note:
Alertmanager
versions belowv0.22.0
are no longer supported. Version must upgraded - manually for resources or use default version bundled with operator config.ServiceAccount
specified forCRD
s. Previously operator didn't perform a check for actual owner ofServiceAccount
. Now it creates and updatesServiceAccount
only if this field is omitted atCRD
definition. It fixes possible ownership race conditions.CRD
s. Operator no longer watches forService
,Secret
,Configmap
changes owned by CRD object. It must reduce logging output, CPU and memory usage for operator.config-reloader-http
port with8435
number for the customer config-reloader containers. Operator may use own config-reloader implementation forVMAuth
,VMAlertmanager
andVMAgent
.configReloaderExtraArgs
forVMAgent
,VMAlert
,VMAuth
andVMAlertmanager
CRDs. It allows to configure config-reloader container.configreloader_last_reload_successful
,configreloader_last_reload_errors_total
,configreloader_config_last_reload_total
,configreloader_k8s_watch_errors_total
,configreloader_secret_content_update_errors_total
,configreloader_last_reload_success_timestamp_seconds
. See this issue for details.Events
into kubernetes API, if any error happened during object reconcile. See this issue for details.Service
generated by operator withuseAsDefault
option set totrue
forserviceSpec
field. See this issue for details.serviceName
field forvmagent
atstatefulMode
with custom service. See this issue for details. Thanks @yilmazostatefulMode
to theheadless
instead ofclusterIP
. See this issue for details.attach_metadata
option under VMServiceScrapeSpec&VMPodScrapeSpec, the same way like prometheus serviceMonitor&podMonitor do. See this issue for details.regex
atrelabelConfig
. See this docs and this issue for details.Sigv4Config
.config-reloader
container. It must improve speed of config updates. See this issue for details.msteams_configs
.targetRefBasicAuth
fieldtargetRef
, which allow to configure basic authorization fortarget_url
. See this issue for details. Thanks @mohammadkhavariproxy_url
, see this issue for details.series_limit
, which can be used to limit the number of unique time series a single scrape target can expose.disable_keep_alive
, before it's misconfigured asdisable_keepalive
and won't work.relabel_debug
andmetric_relabel_debug
, they were deprecated since v1.85.0.v0.42.4
Compare Source
Full Changelog: https://github.com/VictoriaMe
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 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.