build(deps): bump github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring from 0.61.0 to 0.65.1

[dependabot]

Bumps github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring from 0.61.0 to 0.65.1.

Release notes

Sourced from github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring's releases.

0.65.1 / 2022-05-05

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

0.65.0 / 2022-05-04

The main change introduced by this release is the new v1alpha1 ScrapeConfig CRD. This implements the proposal documented in prometheus-operator/prometheus-operator#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

0.64.1 / 2023-04-24

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

0.64.0 / 2023-03-29

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

... (truncated)

Changelog

Sourced from github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring's changelog.

0.65.1 / 2022-05-05

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

0.65.0 / 2022-05-04

The main change introduced by this release is the new v1alpha1 ScrapeConfig CRD. This implements the proposal documented in #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

0.64.1 / 2023-04-24

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

0.64.0 / 2023-03-29

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

... (truncated)

Commits

• b5e9f22 Prep for release v0.65.1 (#5555)
• 135ec55 fix: avoid panic when ScrapeConfig CRD isn't installed (#5550)
• fa7f9eb Release 0.65.0 prep (#5548)
• e77aeaa Merge pull request #5540 from ArthurSens/arthur-company
• bf557c8 Merge pull request #5542 from philipgough/65-prep-1
• b07f92c feat: Add ScrapeConfig CRD (#5335)
• 78ba198 chore: make update-go-deps in prep for release v0.65.0
• 7a88881 Update Arthur's affiliation
• 06b5c41 build(deps): bump github.com/prometheus/client_golang (#5537)
• 34f15c3 chore: update to Kubernetes v1.27.1 (#5530)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

The following labels could not be found: ok-to-test.