This repository has been archived by the owner on Dec 1, 2023. It is now read-only.
chore(deps): update dependency prometheus-crd-source to v0.70.0 #658
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.63.0
->v0.70.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
prometheus-operator/prometheus-operator (prometheus-crd-source)
v0.70.0
: 0.70.0 / 2023-11-30Compare Source
trackTimestampsStaleness
field toServiceMonitor
,PodMonitor
andScrapeConfig
CRDs. #6105persistentVolumeClaimRetentionPolicy
field to thePrometheus
andPrometheusAgent
CRDs. #6038KubernetesSDConfigs
inScrapeConfig
CRD. #6089ScrapeConfig
CRD. #6078 #6009.spec.reloadStrategy
to the Prometheus and PrometheusAgent CRDs. The value can beHTTP
(default if not specified) orProcessSignal
. #5690os.Stdout
. #6085additionalScrapeConfigs
. #6099v0.69.1
: 0.69.1 / 2023-11-09Compare Source
This release is built using Go 1.21.4 which addresses CVE-2023-45283 and CVE-2023-45284.
v0.69.0
: 0.69.0 / 2023-11-03Compare Source
optional
value to be mandatory instead of optional for.spec.additionalScrapeConfigs
configs. #5985prometheus_operator_rule_validation_triggered_total
,prometheus_operator_rule_validation_errors_total
,prometheus_operator_alertmanager_config_validation_triggered_total
andprometheus_operator_alertmanager_config_validation_errors_total
metrics which have been deprecated since v0.55.0. The same information is available from theapiserver_admission_webhook_rejection_count
metric available since Kubernetes v1.16.0. #6024sigv4
field to the Alertmanager endpoints for the Prometheus CRD. #6036userKeyFile
andtokenFile
fields for Pushover to the AlertmanagerConfig CRD. #5886--as
to the operator's CLI arguments for user impersonation. #5906selectors
field for the Kubernetes service discovery to the ScrapeConfig CRD. #6053url_file
for Webhook receiver in the Alertmanager configuration. #5876user_key_file
andtoken_file
for Pushover receiver in the Alertmanager configuration. #5876operator.prometheus.io/version
annotation to the CRD manifests. #6050.spec.scrapeConfigSelector
is defined. #5941stripped-down-crds.yaml
manifest file. #6008v0.68.0
: 0.68.0 / 2023-09-08Compare Source
keep_dropped_targets
to Prometheus, PrometheusAgent, ServiceMonitor, PodMonitor, Probe and ScrapeConfig CRDs. #5897revisionHistoryLimit
. #5773v0.67.1
: 0.67.1 / 2023-08-03Compare Source
[BUGFIX] Avoid skipping AlertmanagerConfig resources for Alertmanager versions prior v0.25.0. #5788
v0.67.0
: 0.67.0 / 2023-07-27Compare Source
spec.scheme
field to the ScrapeConfig CRD. #5679spec.params
field to the ScrapeConfig CRD. #5750spec.scrapeInterval
andspec.scrapeTimeout
fields to the ScrapeConfig CRD. #5742spec.excludedFromEnforcement
(Prometheus CRD). #5577spec.alertmanagerConfiguration.smtp
field to the Alertmanager CRD. #5649v0.66.0
: 0.66.0 / 2023-06-14Compare Source
After research, we noticed how the default CPU requests of the config-reloader container were too high compared to the effective usage. We decided to decrease the default CPU requests from
100m
to10m
. For most environments, this won't make a difference but if you need to increase the values, you can use the-config-reloader-cpu-request
and-config-reloader-cpu-limit
CLI arguments of the Prometheus operator.100m
to10m
. #5539spec.alertmanagerConfiguration.global.PagerdutyURL
to theAlertmanager
CRD. #5469spec.volumeMounts
to theThanosRuler
CRD. #5541spec.remoteWrite.sendNativeHistograms
toPrometheus
andPrometheusAgent
CRDs. #5564spec.tracingConfig
toPrometheus
andPrometheusAgent
CRDs. #5591 #5640followRedirects
field to theRemoteRead
configuration. #5612spec.automountServiceAccountToken
to theAlertmanager
CRD. #5474keep_firing_for
fields forPrometheusRule
CRD. #5651BasicAuth
andAuthorization
support toScrapeConfig
CRD. #5642-kubelet-selector
CLI argument to filter the Kubernetes nodes by labels. #5641\n
) characters. #5566Prometheus
CRD. #5596PrometheusAgent
CRD. #5625v0.65.2
: 0.65.2 / 2023-05-31Compare Source
v0.65.1
: 0.65.1 / 2023-05-05Compare Source
v0.65.0
: 0.65.0 / 2023-05-04Compare Source
The main change introduced by this release is the new v1alpha1 ScrapeConfig CRD. This implements the proposal documented in https://github.com/prometheus-operator/prometheus-operator/pull/5279 and provides a Kubernetes native API to create and manage additional scrape configurations.
To try it, follow the following steps:
example/prometheus-operator-crd/monitoring.coreos.com_scrapeconfigs.yaml
).example/rbac/prometheus-operator/prometheus-operator-cluster-role.yaml
).NOTE: if these conditions aren't met, the operator will start but it won't be able to reconcile the ScrapeConfig resources.
v0.64.1
: 0.64.1 / 2023-04-24Compare Source
/metrics
with PrometheusAgent resources declared. #5511v0.64.0
: 0.64.0 / 2023-03-29Compare Source
This release provides first-class support for running Prometheus in agent mode
with the new
PrometheusAgent
CRD. As the v1alpha1 version tells it, we don'trecommend using it in production but we're eager to hear all possible feedback.
To try it, follow the following steps:
example/prometheus-operator-crd/monitoring.coreos.com_prometheusagents.yaml
).(see
example/rbac/prometheus-operator/prometheus-operator-cluster-role.yaml
).NOTE: if these conditions aren't met, the operator will start but it won't
be able to reconcile the PrometheusAgent resources.
For the first time, the container images associated to this release are signed
using sigstore.
/apis
endpoints from the operator's web server. #5396spec.portName
toweb
. #5350PrometheusAgent
CRD to run Prometheus in agent mode. #5385--reload-timeout
argument to the config-reloader binary which controls how long the program will wait for the reload operation to complete (default: 30s). #5349ReadTimeout
andReadHeaderTimeout
to 30s for Prometheus operator and config-reloader to avoid potential slowloris attacks. #5340DropEqual
andKeepEqual
relabeling actions. #5368PrometheusRule
objects instead of failing the reconciliation of Prometheus and ThanosRuler objects. #5221spec.thanos.blockSize
field to thePrometheus
CRD. #5360spec.thanos.configTimeout
andspec.thanos.configInterval
to the Prometheus CRD. #5399spec.alertmanagerConfiguration.global.slackApiUrl
field to theAlertmanager
CRD. #5383spec.alertmanagerConfiguration.global.opsGenieApiUrl
andspec.alertmanagerConfiguration.global.opsGenieApiKey
fields to theAlertmanager
CRD. #5422init-config-reloader
init container to avoid a restart of the Alertmanager'sconfig-reloader
container when the pod starts. #5358Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 has been generated by Mend Renovate. View repository job log here.