Bump github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring from 0.52.1 to 0.57.0

[dependabot]

Bumps github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring from 0.52.1 to 0.57.0.

Release notes

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

0.57.0 / 2022-06-02

The main change introduced by this release is a new v1beta1 API version for the AlertmanagerConfig CRD.

Changes compared to the v1alpha1 API:

• Renamed spec.muteTimeIntervals field to to spec.timeIntervals.
• Removed regex field from the Matcher type.
• Replaced all v1.SecretKeySelector types by the SecretKeySelector type
  • Removed optional field.
  • name and key fields are required.

As a pre-requisite, you need to deploy the admission webhook and configure the conversion webhook in the AlertmanagerConfig CRD object so that users can use both v1alpha1 and v1beta1 versions at the same time. There are more details in Documentation/user-guides/webhook.md about the webhook configuration.

Because of the conversion webhook requirement, the new version is an opt-in feature: the bundle.yaml file and the manifests from example/prometheus-operator-crd don't deploy the new API version (the manifests to enable the v1beta1 version are under the example/prometheus-operator-crd-full directory). We will wait until v0.59.0 (at least) before enabling the new API version by default.

• [CHANGE] Added validations at the API level for the time-based fields of the ThanosRuler CRD. #4815
• [CHANGE] Added validations at the API level for the OpsGenie's responders field of the AlertmanagerConfig CRD. #4725
• [FEATURE] Added v1beta1 version for AlertmanagerConfig CRD. #4709
• [FEATURE] Added support for Telegram receiver in the AlertmanagerConfig CRD. #4726
• [FEATURE] Added updateAlerts field to the OpsGenie configuration of the AlertmanagerConfig CRD. #4726
• [FEATURE] Added hostAliases field to the the Alertmanager, Prometheus and ThanosRuler CRDs. #4787
• [ENHANCEMENT] Added configuration option in the jsonnet mixins to specify the aggregation labels. #4814
• [ENHANCEMENT] Added attachMetadata field to the PodMonitor CRD. #4792
• [BUGFIX] Fixed the curl command for exec probes when listenLocal is set to true in the Prometheus object. It avoids temporary service outage due to long WAL replays. #4804

0.56.3 / 2022-05-23

• [BUGFIX] Fixed errors for Alertmanager configurations using the new entity, actions and opsgenie_api_key_file fields. #4797
• [BUGFIX] Fixed high CPU usage by reducing the number of number of reconciliations on Prometheus objects. #4798 #4806

0.56.2 / 2022-05-09

• [BUGFIX] Fix StatefulSet spec's generation to be determistic when spec.containers is not empty. #4772

0.56.1 / 2022-05-03

• [BUGFIX] Avoid unnecessary updates of the Prometheus StatefulSet object. #4762

0.56.0 / 2022-04-20

• [CHANGE] Added validation at the API level for size-based fields of the Prometheus CRD. #4661
• [CHANGE] Added validation at the API level for log level and format fields of the Alertmanager, Prometheus and ThanosRuler CRDs. #4638
• [CHANGE] Added validation at the API level for duration and time-based fields of the Prometheus CRD. #4684
• [CHANGE] Added shortnames for custom resources (amcfg for AlertmanagerConfig, am for Alertmanager, pmon for PodMonitor, prb for Probe, prom for Prometheus, smon for ServiceMonitor, ruler for Thanos Ruler). #4680
• [FEATURE] Added status subresource to the Prometheus CRD. #4580
• [ENHANCEMENT] Added excludedFromEnforce field to the Prometheus CRD. It allows to define PodMonitor, ServiceMonitor, Probe or PrometheusRule objects for which the namespace label enforcement (if enabled) should not be applied. This deprecates prometheusRulesExcludedFromEnforce which is still supported but users are encouraged to migrate to the new field. #4397
• [ENHANCEMENT] Added enableRemoteWriteReceiver field to the Prometheus CRD. #4633
• [ENHANCEMENT] Added entity and actions fields for the OpsGenie receiver to the AlertmanagerConfig CRD. #4697
• [ENHANCEMENT] Added prometheus_operator_reconcile_duration_seconds histogram metric. #4706
• [BUGFIX] Added support for opsgenie_api_key_file and api_key_file in the generated Alertmanager configuration. #4666 #4738

0.55.1 / 2022-03-26

• [BUGFIX] Fixed Prometheus configuration when spec.queryLogFile has no path ("query.log" for instance). #4683

... (truncated)

Changelog

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

0.57.0 / 2022-06-02

The main change introduced by this release is a new v1beta1 API version for the AlertmanagerConfig CRD.

Changes compared to the v1alpha1 API:

• Renamed spec.muteTimeIntervals field to to spec.timeIntervals.
• Removed regex field from the Matcher type.
• Replaced all v1.SecretKeySelector types by the SecretKeySelector type
  • Removed optional field.
  • name and key fields are required.

As a pre-requisite, you need to deploy the admission webhook and configure the conversion webhook in the AlertmanagerConfig CRD object so that users can use both v1alpha1 and v1beta1 versions at the same time. There are more details in Documentation/user-guides/webhook.md about the webhook configuration.

Because of the conversion webhook requirement, the new version is an opt-in feature: the bundle.yaml file and the manifests from example/prometheus-operator-crd don't deploy the new API version (the manifests to enable the v1beta1 version are under the example/prometheus-operator-crd-full directory). We will wait until v0.59.0 (at least) before enabling the new API version by default.

• [CHANGE] Added validations at the API level for the time-based fields of the ThanosRuler CRD. #4815
• [CHANGE] Added validations at the API level for the OpsGenie's responders field of the AlertmanagerConfig CRD. #4725
• [FEATURE] Added v1beta1 version for AlertmanagerConfig CRD. #4709
• [FEATURE] Added support for Telegram receiver in the AlertmanagerConfig CRD. #4726
• [FEATURE] Added updateAlerts field to the OpsGenie configuration of the AlertmanagerConfig CRD. #4726
• [FEATURE] Added hostAliases field to the the Alertmanager, Prometheus and ThanosRuler CRDs. #4787
• [ENHANCEMENT] Added configuration option in the jsonnet mixins to specify the aggregation labels. #4814
• [ENHANCEMENT] Added attachMetadata field to the PodMonitor CRD. #4792
• [BUGFIX] Fixed the curl command for exec probes when listenLocal is set to true in the Prometheus object. It avoids temporary service outage due to long WAL replays. #4804

0.56.3 / 2022-05-23

• [BUGFIX] Fixed errors for Alertmanager configurations using the new entity, actions and opsgenie_api_key_file fields. #4797
• [BUGFIX] Fixed high CPU usage by reducing the number of number of reconciliations on Prometheus objects. #4798 #4806

0.56.2 / 2022-05-09

• [BUGFIX] Fix StatefulSet spec's generation to be determistic when spec.containers is not empty. #4772

0.56.1 / 2022-05-03

• [BUGFIX] Avoid unnecessary updates of the Prometheus StatefulSet object. #4762

0.56.0 / 2022-04-20

• [CHANGE] Added validation at the API level for size-based fields of the Prometheus CRD. #4661

... (truncated)

Commits

• 5db6996 Merge pull request #4831 from simonpasquier/cut-0.57
• 35d3181 *: cut v0.57.0
• e455740 Allow user to configure hostAliases for Alertmanager, Prometheus and (#4787)
• 8ed1224 Merge pull request #4825 from prometheus-operator/dependabot/go_modules/sigs....
• 06b2b4e build(deps): bump sigs.k8s.io/controller-runtime from 0.11.2 to 0.12.1
• 1829e37 *: add v1beta1 for AlertmanagerConfig CRD (#4709)
• b3e71e5 Merge pull request #4815 from slashpai/openapi_validation
• 64ee359 Merge pull request #4819 from prometheus-operator/dependabot/go_modules/k8s.i...
• e3dc10b build(deps): bump k8s.io/component-base from 0.24.0 to 0.24.1
• f85ee4a Merge pull request #4818 from prometheus-operator/dependabot/go_modules/k8s.i...
• 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]

Superseded by #14.