search

openshift / file-integrity-operator

Operator providing OpenShift cluster node file integrity checking
Apache License 2.0
31 stars 27 forks source link

Bump github.com/prometheus-operator/prometheus-operator/pkg/client from 0.65.2 to 0.68.0 #433

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps github.com/prometheus-operator/prometheus-operator/pkg/client from 0.65.2 to 0.68.0.

Release notes

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

0.68.0 / 2023-09-08

  • [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

0.67.1 / 2023-08-03

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

0.67.0 / 2023-07-27

  • [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

0.66.0 / 2023-06-14

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

... (truncated)

Changelog

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

0.68.0 / 2023-09-06

  • [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

0.67.1 / 2023-08-03

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

0.67.0 / 2023-07-27

  • [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

0.66.0 / 2023-06-14

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

... (truncated)

Commits
  • 52526e3 Prepare 0.68 release (#5896)
  • fae174e Merge pull request #5900 from slashpai/update_golden
  • 1687f32 test: update ScrapeConfig tests to use golden files
  • 0a93915 feat: add keep_dropped_targets limit to CRDs (#5897)
  • 74505c3 Merge pull request #5891 from simonpasquier/fix-empty-status-on-sts-creation-...
  • 51c3ea0 feat: add bot_token_file in TelegramConfig (#5882)
  • eefcc29 Update dependencies before 0.68 release (#5895)
  • e771085 Merge pull request #5894 from prometheus-operator/dependabot/go_modules/golan...
  • cc224d7 Merge pull request #5893 from prometheus-operator/dependabot/go_modules/githu...
  • 8cd21f0 build(deps): bump golang.org/x/net from 0.14.0 to 0.15.0
  • Additional commits viewable in compare view


Dependabot compatibility score

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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
openshift-ci[bot] commented 1 year ago

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

I'm waiting for a openshift 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.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
rhmdnd commented 1 year ago

This needs https://github.com/openshift/file-integrity-operator/pull/437 to land to fix some of the test failures.

rhmdnd commented 1 year ago

@dependabot rebase

openshift-ci[bot] commented 1 year ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dependabot[bot], rhmdnd

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

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/openshift/file-integrity-operator/blob/master/OWNERS)~~ [rhmdnd] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
openshift-ci[bot] commented 1 year ago

@dependabot[bot]: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).