chore(deps): update dependency victoria-metrics-operator to v0.51.1 #628
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:
v0.50.0
->v0.51.1
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
VictoriaMetrics/operator (victoria-metrics-operator)
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.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.