-
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.53.0 #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
2d1cb9a
to
2914bf4
Compare
2914bf4
to
a38310e
Compare
a38310e
to
be42126
Compare
be42126
to
b28f9a7
Compare
b28f9a7
to
65a5694
Compare
65a5694
to
6bca76b
Compare
6bca76b
to
ab4c03c
Compare
ab4c03c
to
e9291b8
Compare
e9291b8
to
c9336d1
Compare
c9336d1
to
b88c6fe
Compare
b88c6fe
to
ea40519
Compare
ea40519
to
2ad5ff3
Compare
2ad5ff3
to
e3efe32
Compare
0a62ca2
to
d69b6dd
Compare
d69b6dd
to
36498dc
Compare
36498dc
to
abba0a1
Compare
abba0a1
to
ce87d6a
Compare
ce87d6a
to
e310f79
Compare
e310f79
to
82ae251
Compare
82ae251
to
c5c493e
Compare
c5c493e
to
fd742b6
Compare
fd742b6
to
02bb1d8
Compare
02bb1d8
to
403a287
Compare
403a287
to
595dcf8
Compare
595dcf8
to
ea105c0
Compare
ea105c0
to
54e0edd
Compare
54e0edd
to
0f720dd
Compare
0f720dd
to
02308f6
Compare
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.49.1
->0.53.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
VictoriaMetrics/operator (VictoriaMetrics/operator)
v0.53.0
Compare Source
v0.53.0
Release date: 05 Feb 2025
SECURITY: upgrade Go builder from Go1.23.4 to Go1.23.5. See the list of issues addressed in Go1.23.5.
Dependency: vmoperator: Updated default versions for VM apps to v1.110.0 version
FEATURE: vmalertmanagerconfig: add
thread_message_id
totelegram_configs
definition. It's supported by alertmanager v0.28.0+. See this issue for details.FEATURE: vlogs: support VLogs in VMUser targetRefs.crd
BUGFIX: vmoperator: properly check
Pod
state duringStatefulSet
rolling upgrade procedure. See this issue for details.BUGFIX: vmagent: properly upscale on
shardCount
change. See this issue for details.BUGFIX: vmauth: properly apply
vmuser
changes. See this PR for details.v0.52.0
Compare Source
v0.52.0
Release date: 21 Jan 2025
Dependency: vmoperator: Updated default versions for VM apps to v1.109.1 version
Dependency: vmoperator: Updated default version for VictoriaLogs app to v1.6.1 version
FEATURE: vmscrapeconfig: allow multiple values for
zone
atgceSDConfigs
. See this issue for details.FEATURE: vmoperator: decrease latency of generated configuration updates. Previously, configuration was update after status of child objects were changed. It could take significant time at large scale. See this issue for details.
FEATURE: vmoperator: reduce load on Kubernetes API server at prometheus-converter client.
FEATURE: vmoperator: change default value for
client.qps=50
andclient.burst=100
in order to improve operator performance on scale. See this issue for details.FEATURE: vmoperator: add new flag
controller.statusLastUpdateTimeTTL=1h
to control staleness detection atstatus.conditions
field. If operator serves large amount of object ( > 5_000) value for it should be increased.FEATURE: vmoperator: add more context to the
failed
status with the reason and logs of crashed container. See this issue for details.FEATURE: vmoperator: Properly expose service ports for
VMServiceScrape
generated for CRD objects by operator. Add-vmbackupmanager
suffix to theVMServiceScrape
job name and expose only well-knownhttp
port. See this issue for details.BUGFIX: vmagent: properly build
relabelConfigs
with empty string values forseparator
andreplacement
fields. See this issue for details.BUGFIX: converter: properly format
regex
single value expression at Prometheus Operator CRDrelabelings
andmetricsRelabelings
. See this issue for details.BUGFIX: vmoperator: keep
spec.template.annotations
added by 3rd party tools, kikekubectl rollout restart
. See this issue for details.v0.51.3
Compare Source
v0.51.3
Release date: 8 Jan 2025
pods
withstatefulMode
andshardCount
defined.volumeMount
for externalstorageDataPath
volume
.serviceAccount
forrequestsLoadBalancer
Deployment
. See this issue for details.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
.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.