Update module github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring to v0.68.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring	require	minor	v0.63.0 -> v0.68.0

---

Release Notes

prometheus-operator/prometheus-operator (github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring)

v0.68.0: 0.68.0 / 2023-09-08

Compare Source

• [FEATURE] Add support for Webex receiver to the AlertmanagerConfig CRD. #​5305
• [FEATURE] Add support for Bot Token File for Telegram receiver in AlermanagerConfig CRD. #​5882
• [FEATURE] Add support for MetricRelabelings to the ScrapeConfig CRD. #​5805
• [FEATURE] Add support for DNS service discovery fields to the ScrapeConfig CRD. #​5866
• [FEATURE] Add support for keep_dropped_targets to Prometheus, PrometheusAgent, ServiceMonitor, PodMonitor, Probe and ScrapeConfig CRDs. #​5897
• [FEATURE] Don't trigger reconcile loops if statefulsets have different revisionHistoryLimit. #​5773
• [ENHANCEMENT] Decrease CPU usage when reconciling ThanosRuler resources. #​5784
• [BUGFIX] Fix sharding in Probe CRD. #​5735
• [BUGFIX] Fix text-only email configs in AlertmanagerConfig CRD. #​5804
• [BUGFIX] Fix rejecting PodMonitor, ServiceMonitor, Probes and ScrapeConfigs with invalid relabelings. #​5841 #​5856
• [BUGFIX] Fix Kubernetes Service Discovery in ScrapeConfig CRD. #​5871
• [BUGFIX] Fix reserved labels being overriden by external labels. #​5888
• [BUGFIX] Fix updating Status of Prometheus, Alertmanager and ThanosRuler even the operator fails to update their statefulsets. #​5891

v0.67.1: 0.67.1 / 2023-08-03

Compare Source

[BUGFIX] Avoid skipping AlertmanagerConfig resources for Alertmanager versions prior v0.25.0. #​5788

v0.67.0: 0.67.0 / 2023-07-27

Compare Source

• [FEATURE] Add spec.scheme field to the ScrapeConfig CRD. #​5679
• [FEATURE] Add spec.params field to the ScrapeConfig CRD. #​5750
• [FEATURE] Add spec.scrapeInterval and spec.scrapeTimeout fields to the ScrapeConfig CRD. #​5742
• [FEATURE] Add support for TLS configuration to the ScrapeConfig CRD. #​5710
• [FEATURE] Add support for scrape limits to the ScrapeConfig CRD. #​5658
• [FEATURE] Add support for Kubernetes node service discovery to the ScrapeConfig CRD. #​5675
• [FEATURE] Add support for Consul service discovery to the ScrapeConfig CRD. #​5709
• [FEATURE] Add support for ScrapeConfig objects to spec.excludedFromEnforcement (Prometheus CRD). #​5577
• [FEATURE] Add support for global scrape limits to the Prometheus CRD. #​5646
• [FEATURE] Add spec.alertmanagerConfiguration.smtp field to the Alertmanager CRD. #​5649
• [FEATURE] Add support for Discord integration to the AlertmanagerConfig CRD. #​5671
• [ENHANCEMENT] (jsonnet) expose resource settings for the reloader. #​5768
• [BUGFIX] Avoid deadlock of the config reloader when the initial configuration is invalid. #​5743
• [BUGFIX] Reload the Alertmanager configuration when templates are modified. #​5727

v0.66.0: 0.66.0 / 2023-06-14

Compare 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 to 10m. 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.

• [CHANGE] Decrease the default CPU requests for the config-reloader container from 100m to 10m. #​5539
• [FEATURE] Add spec.alertmanagerConfiguration.global.PagerdutyURL to the Alertmanager CRD. #​5469
• [FEATURE] Add spec.volumeMounts to the ThanosRuler CRD. #​5541
• [FEATURE] Add spec.remoteWrite.sendNativeHistograms to Prometheus and PrometheusAgent CRDs. #​5564
• [FEATURE] Add spec.tracingConfig to Prometheus and PrometheusAgent CRDs. #​5591 #​5640
• [FEATURE] Add followRedirects field to the RemoteRead configuration. #​5612
• [FEATURE] Add spec.automountServiceAccountToken to the Alertmanager CRD. #​5474
• [FEATURE] Support keep_firing_for fields for PrometheusRule CRD. #​5651
• [FEATURE] Allow to add custom annotations to all resources managed by the operator. #​5626
• [FEATURE] Add BasicAuth and Authorization support to ScrapeConfig CRD. #​5642
• [ENHANCEMENT] Add -kubelet-selector CLI argument to filter the Kubernetes nodes by labels. #​5641
• [BUGFIX] Fix bug with logs that don't end with new line(\n) characters. #​5566
• [BUGFIX] Fix Prometheus and Alertmanager not picking up the web server's certificate after renewal. #​5535
• [BUGFIX] Fix config-reloader not handling SIGTERM signal. #​5617
• [BUGFIX] Fix Thanos volume name when using VolumeClaimTemplate in Prometheus CRD. #​5596
• [BUGFIX] Fix WAL Compression configuration for PrometheusAgent CRD. #​5625
• [BUGFIX] Fix DNS name resolution for individual ThanosRuler pods. #​5632

v0.65.2: 0.65.2 / 2023-05-31

Compare Source

• [BUGFIX] Fix relabeling issue in ScrapeConfig CRD. #​5611

v0.65.1: 0.65.1 / 2023-05-05

Compare Source

• [BUGFIX] Fix panic when ScrapeConfig CRD is not installed. #​5550

v0.65.0: 0.65.0 / 2023-05-04

Compare 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:

1. Install the new CRD in the cluster (see example/prometheus-operator-crd/monitoring.coreos.com_scrapeconfigs.yaml).
2. Update the Prometheus operator's RBAC permissions to manage ScrapeConfig resources (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 ScrapeConfig resources.

• [FEATURE] Add the status subresource for the ThanosRuler CRD. #​5520
• [FEATURE] Add spec.web.timeout and spec.web.getConcurrency to the Alertmanager CRD. #​5478
• [FEATURE] Add spec.groups[].limit to the Prometheus CRD. #​4999
• [FEATURE] Add ScrapeConfig CRD. #​5335
• [ENHANCEMENT] Set a default for seccompProfile on the operator and webhook Deployments to RuntimeDefault. #​5477
• [ENHANCEMENT] Add optional liveness and readiness probes to prometheus-config-reloader. This can be enabled via the --enable-config-reloader-probes CLI flag. #​5449
• [BUGFIX] Don't start the PrometheusAgent controller if the CRD isn't present or the operator lacks permissions. #​5476
• [BUGFIX] Declare spec.rules optional in PrometheusRule CRD. #​5481
• [BUGFIX] Fix incorrect metric counter value for failed sync status. #​5533

v0.64.1: 0.64.1 / 2023-04-24

Compare Source

• [BUGFIX] Fix panic when scraping /metrics with PrometheusAgent resources declared. #​5511

v0.64.0: 0.64.0 / 2023-03-29

Compare 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't
recommend using it in production but we're eager to hear all possible feedback.

To try it, follow the following steps:

1. Install the new CRD in the cluster (see
   example/prometheus-operator-crd/monitoring.coreos.com_prometheusagents.yaml).
2. Update the Prometheus operator's RBAC permissions to manage PrometheusAgents resources
   (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.

• [CHANGE] Remove the /apis endpoints from the operator's web server. #​5396
• [CHANGE] Set default default value of spec.portName to web. #​5350
• [FEATURE] Add v1alpha1 PrometheusAgent CRD to run Prometheus in agent mode. #​5385
• [FEATURE] Add --reload-timeout argument to the config-reloader binary which controls how long the program will wait for the reload operation to complete (default: 30s). #​5349
• [ENHANCEMENT] Set web server's ReadTimeout and ReadHeaderTimeout to 30s for Prometheus operator and config-reloader to avoid potential slowloris attacks. #​5340
• [ENHANCEMENT] Add support for DropEqual and KeepEqual relabeling actions. #​5368
• [ENHANCEMENT] Drop invalid PrometheusRule objects instead of failing the reconciliation of Prometheus and ThanosRuler objects. #​5221
• [ENHANCEMENT] Add spec.thanos.blockSize field to the Prometheus CRD. #​5360
• [ENHANCEMENT] Add spec.thanos.configTimeout and spec.thanos.configInterval to the Prometheus CRD. #​5399
• [ENHANCEMENT] Add spec.alertmanagerConfiguration.global.slackApiUrl field to the Alertmanager CRD. #​5383
• [ENHANCEMENT] Add spec.alertmanagerConfiguration.global.opsGenieApiUrl and spec.alertmanagerConfiguration.global.opsGenieApiKey fields to the Alertmanager CRD. #​5422
• [ENHANCEMENT] Reduce the operator's memory usage by using metadata informers for Kubernetes secrets and configmaps. #​5424 #​5448
• [BUGFIX] Add init-config-reloader init container to avoid a restart of the Alertmanager's config-reloader container when the pod starts. #​5358

---

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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v0.68.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.