Bump github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring from 0.79.2 to 0.80.1

[dependabot]

Bumps github.com/prometheus-operator/prometheus-operator/pkg/apis/monitoring from 0.79.2 to 0.80.1.

Release notes

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

0.80.1 / 2025-02-19

• [BUGFIX] Fix msteamsv2_configs to work with either webhook_url or webhook_url_file. #7352

0.80.0 / 2025-02-04

• [CHANGE] Add more API validations to the ScrapeConfig CRD. #7231 #7220 #7215 #7238 #7244 #7255
• [FEATURE] Add serviceName field to the Prometheus and PrometheusAgent CRDs. #6687
• [FEATURE] Add keepIdentifyingResourceAttributes field in OTLPConfig for Prometheus and PrometheusAgent CRDs. #7240
• [FEATURE] Add fallbackScrapeProtocol field to ScrapeClass for Prometheus and PrometheusAgent CRDs. #7288
• [FEATURE] Support MSTeamsV2Config receiver in Alertmanager configuration Secret. #7296
• [FEATURE] Support JiraConfig and RocketChat receivers in Alertmanager configuration secret. #7315
• [FEATURE] Support global smtp_tls_config field in Alertmanager configuration secret. #7316
• [FEATURE] Add timeout field in Webhook receiver in Alertmanager configuration Secret. #7312
• [FEATURE] Add content, username and avatarUrl fields in Discord receiver in Alertmanager configuration secret. #7313
• [FEATURE] Add scrapeFailureLogFile field to the Prometheus and PrometheusAgent CRDs. #7038 #7311
• [BUGFIX] Validate respective api URL field in PagerDutyConfigs, DiscordConfigs, SlackConfigs and WebhookConfigs in AlertManagerConfig CRD. #6585

Changelog

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

0.80.1 / 2025-02-19

• [BUGFIX] Fix msteamsv2_configs to work with either webhook_url or webhook_url_file. #7352

0.80.0 / 2025-02-04

• [CHANGE] Add more API validations to the ScrapeConfig CRD. #7231 #7220 #7215 #7238 #7244 #7255
• [FEATURE] Add serviceName field to the Prometheus and PrometheusAgent CRDs. #6687
• [FEATURE] Add keepIdentifyingResourceAttributes field in OTLPConfig for Prometheus and PrometheusAgent CRDs. #7240
• [FEATURE] Add fallbackScrapeProtocol field to ScrapeClass for Prometheus and PrometheusAgent CRDs. #7288
• [FEATURE] Support MSTeamsV2Config receiver in Alertmanager configuration Secret. #7296
• [FEATURE] Support JiraConfig and RocketChat receivers in Alertmanager configuration secret. #7315
• [FEATURE] Support global smtp_tls_config field in Alertmanager configuration secret. #7316
• [FEATURE] Add timeout field in Webhook receiver in Alertmanager configuration Secret. #7312
• [FEATURE] Add content, username and avatarUrl fields in Discord receiver in Alertmanager configuration secret. #7313
• [FEATURE] Add scrapeFailureLogFile field to the Prometheus and PrometheusAgent CRDs. #7038 #7311
• [BUGFIX] Validate respective api URL field in PagerDutyConfigs, DiscordConfigs, SlackConfigs and WebhookConfigs in AlertManagerConfig CRD. #6585

Commits

• 4126d60 Merge pull request #7358 from slashpai/cut-0.80.1
• e8a7162 chore: cut v0.80.1
• 85b1639 Merge pull request #7352 from heliapb/fix/msteamsv2_config_r0_80
• 53b60e1 fix - MSTeamsV2 config
• c740cff Merge pull request #7354 from simonpasquier/backport-c0e32a49d
• 4130922 test: skip DNS service discovery tests
• 56cc9ee Merge pull request #7318 from slashpai/cut-release-0.80
• fead04d chore: update changelog for v0.80.0 updates
• 6f920d7 feat: Refactor IonosSDConfig (#7255)
• 6f3c19a chore: Refactor OpenStackSDConfig (#7244)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jpinsonneau for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a netobserv member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.