Skip to content

NO-ISSUE: [bot] Bump openshift/prometheus-operator to v0.93.0 - #388

Merged
openshift-merge-bot[bot] merged 113 commits into
openshift:mainfrom
rhobs:automated-updates-main
Aug 3, 2026
Merged

NO-ISSUE: [bot] Bump openshift/prometheus-operator to v0.93.0#388
openshift-merge-bot[bot] merged 113 commits into
openshift:mainfrom
rhobs:automated-updates-main

Conversation

@openshift-monitoring-bot

@openshift-monitoring-bot openshift-monitoring-bot Bot commented Jul 29, 2026

Copy link
Copy Markdown

Description

This is an automated version bump from CI.
The logs for this run can be found in the syncbot repo actions.

yugstar and others added 30 commits June 17, 2026 04:54
The ScrapeConfig developer guide lists Kubernetes Service Discovery
first among the Tier-1 mechanisms and has example sections for
static_config, file_sd and http_sd, but had no kubernetes_sd example.

Add one showing a minimal node-discovery ScrapeConfig, noting that role
is required and capitalized (e.g. Node, not node) and that in-cluster
Prometheus discovers the API server and credentials automatically, with
pointers to namespaces, selectors and relabelings.

Closes prometheus-operator#6517

Signed-off-by: Aman Raj <aman.yug@gmail.com>
Signed-off-by: dongjiang <dongjiang1989@126.com>
…x-misspelling

Fix(docs): fix misspelling in rules_test.go comment
Signed-off-by: dongjiang <dongjiang1989@126.com>
Signed-off-by: dongjiang <dongjiang1989@126.com>
…us-operator#8629)

The ScrapeConfig developer guide lists Kubernetes Service Discovery
first among the Tier-1 mechanisms and has example sections for
static_config, file_sd and http_sd, but had no kubernetes_sd example.

Add one showing a minimal node-discovery ScrapeConfig, noting that role
is required and capitalized (e.g. Node, not node) and that in-cluster
Prometheus discovers the API server and credentials automatically, with
pointers to namespaces, selectors and relabelings.

Closes prometheus-operator#6517

Signed-off-by: Aman Raj <aman.yug@gmail.com>
Bumps the github-actions-deps group with 1 update: [actions/checkout](https://github.com/actions/checkout).


Updates `actions/checkout` from 6.0.3 to 7.0.0
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v6.0.3...v7.0.0)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: 7.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
…dependabot/github_actions/github-actions-deps-2217aebe03

build(deps): bump actions/checkout from 6.0.3 to 7.0.0 in the github-actions-deps group
The test requires experimental features which aren't all supported by
Prometheus v2.

Signed-off-by: Simon Pasquier <spasquie@redhat.com>
Bumps [github.com/prometheus-community/prom-label-proxy](https://github.com/prometheus-community/prom-label-proxy) from 0.13.0 to 0.14.0.
- [Release notes](https://github.com/prometheus-community/prom-label-proxy/releases)
- [Changelog](https://github.com/prometheus-community/prom-label-proxy/blob/main/CHANGELOG.md)
- [Commits](prometheus-community/prom-label-proxy@v0.13.0...v0.14.0)

---
updated-dependencies:
- dependency-name: github.com/prometheus-community/prom-label-proxy
  dependency-version: 0.14.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
…dependabot/go_modules/github.com/prometheus-community/prom-label-proxy-0.14.0

build(deps): bump github.com/prometheus-community/prom-label-proxy from 0.13.0 to 0.14.0
Bumps the github-actions-deps group with 1 update: [actions/setup-go](https://github.com/actions/setup-go).


Updates `actions/setup-go` from 6.4.0 to 6.5.0
- [Release notes](https://github.com/actions/setup-go/releases)
- [Commits](actions/setup-go@v6.4.0...v6.5.0)

---
updated-dependencies:
- dependency-name: actions/setup-go
  dependency-version: 6.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
…dependabot/github_actions/github-actions-deps-9b7bde0b82

build(deps): bump actions/setup-go from 6.4.0 to 6.5.0 in the github-actions-deps group
ShellCheck release use architecture names that do not always match
Go's GOARCH values. This commit maps GOARCH to the matching ShellCheck architecture
before building the download URL.

Fixes prometheus-operator#8621

Signed-off-by: vprashar2929 <vibhu.sharma2929@gmail.com>
…ellcheck

fix(makefile): support shellcheck on arm64
…ometheus-v2-tests

test: skip testPrometheusRuleWithParserOptions with Prometheus v2
…perator#8628)

* add useAWSHTTPClient

Signed-off-by: dongjiang <dongjiang1989@126.com>

* update make gen

Signed-off-by: dongjiang <dongjiang1989@126.com>

---------

Signed-off-by: dongjiang <dongjiang1989@126.com>
validateOpenStackSDConfigs is the only SD validator that never loads its tlsConfig into the asset store, so its secret references are not validated and the assets are not mounted, even though the config generator still emits them via addSafeTLStoYaml. Add the missing AddSafeTLSConfig call, matching the other SD validators and the Consul OAuth2 fix in prometheus-operator#8644.

Signed-off-by: greymoth-jp <m.hirakawa07@icloud.com>
…stack-sd-tls-asset-store

fix: load OpenStack SD TLS config into the asset store
Bumps the github-actions-deps group with 1 update: [imjasonh/setup-crane](https://github.com/imjasonh/setup-crane).


Updates `imjasonh/setup-crane` from 0.6 to 0.7
- [Release notes](https://github.com/imjasonh/setup-crane/releases)
- [Commits](imjasonh/setup-crane@59c71e9...feee3b6)

---
updated-dependencies:
- dependency-name: imjasonh/setup-crane
  dependency-version: '0.7'
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
…dependabot/github_actions/github-actions-deps-4b8b8c3881

build(deps): bump imjasonh/setup-crane from 0.6 to 0.7 in the github-actions-deps group
…heus-operator#8506)

* alertmanager: add updateMessage in Slack Config CR

to support the new field introduced in AM 0.32.0

* alertmanager: update doc

fix typo

* alertmanager: update doc

regenerate to match the updated version

* alertmanager: add field to slack receiver

to support update message

* alertmanager: update test case

change field to be message text

* trigger ci

* alertmanager: update lib name

to fix compile issue

* alertmanager: update test case

try to fix panic

* alertmanager: move version check test case

to check under operator

* alertmanager: update test case

change golden file back

* alertmanager: update test case to reflect the real check for prometheus

as it requires the specific api url and bot token to be set

* alertmanager: update golden file

change the config structure to match the real output

* alertmanager: update logic check for update message

add slack api url check

* trigger ci

* trigger ci

* alertmanager: update error message

* alertmanager: add api url for test validation

to ensure it is validated like alertmanager

* alertmanager: add test case to validate check

* alertmanager: add debug in test case

* alertmanager: update pointer create

change ptr.To to new

* alertmanager: add test case

* alertmanager: update url assignment

to assign to the out of scope variable

* alertmanager: remove debug

* alertmanager: update variable

delete duplicate

* trigger ci

* alertmanager: update test cases

to reflect the result
This commit adds validation markers to ensure that fields declared
as uint32/uint64 accept only positive integers. With the markers, the
Kubernetes API won't reject negative values which would blow up at the
operator level (the conversion from YAML to Go fails).

While technically an API change, users facing the situation today are
already in trouble since the operator can't reconcile their resources.

Signed-off-by: Simon Pasquier <spasquie@redhat.com>
This commit adds validation markers to ensure that fields declared
as uint32/uint64 accept only positive integers. With the markers, the
Kubernetes API won't reject negative values which would blow up at the
operator level (the conversion from YAML to Go fails).

While technically an API change, users facing the situation today are
already in trouble since the operator can't reconcile their resources.

Signed-off-by: Simon Pasquier <spasquie@redhat.com>
Bumps [github.com/prometheus/exporter-toolkit](https://github.com/prometheus/exporter-toolkit) from 0.16.0 to 0.17.1.
- [Release notes](https://github.com/prometheus/exporter-toolkit/releases)
- [Commits](prometheus/exporter-toolkit@v0.16.0...v0.17.1)

---
updated-dependencies:
- dependency-name: github.com/prometheus/exporter-toolkit
  dependency-version: 0.17.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
…dependabot/go_modules/github.com/prometheus/exporter-toolkit-0.17.1

build(deps): bump github.com/prometheus/exporter-toolkit from 0.16.0 to 0.17.1
simonpasquier and others added 6 commits July 28, 2026 14:14
Signed-off-by: Simon Pasquier <spasquie@redhat.com>
Bumps the github-actions-deps group with 2 updates: [docker/login-action](https://github.com/docker/login-action) and [actions/stale](https://github.com/actions/stale).


Updates `docker/login-action` from 4.5.1 to 4.5.2
- [Release notes](https://github.com/docker/login-action/releases)
- [Commits](docker/login-action@abd2ef4...371161b)

Updates `actions/stale` from 10.4.0 to 11.0.0
- [Release notes](https://github.com/actions/stale/releases)
- [Changelog](https://github.com/actions/stale/blob/main/CHANGELOG.md)
- [Commits](actions/stale@v10.4.0...v11.0.0)

---
updated-dependencies:
- dependency-name: docker/login-action
  dependency-version: 4.5.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions-deps
- dependency-name: actions/stale
  dependency-version: 11.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: Simon Pasquier <spasquie@redhat.com>
…theus-operator#8726)

Bumps the github-actions-deps group with 2 updates: [docker/login-action](https://github.com/docker/login-action) and [actions/stale](https://github.com/actions/stale).


Updates `docker/login-action` from 4.5.1 to 4.5.2
- [Release notes](https://github.com/docker/login-action/releases)
- [Commits](docker/login-action@abd2ef4...371161b)

Updates `actions/stale` from 10.4.0 to 11.0.0
- [Release notes](https://github.com/actions/stale/releases)
- [Changelog](https://github.com/actions/stale/blob/main/CHANGELOG.md)
- [Commits](actions/stale@v10.4.0...v11.0.0)

---
updated-dependencies:
- dependency-name: docker/login-action
  dependency-version: 4.5.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions-deps
- dependency-name: actions/stale
  dependency-version: 11.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
v0.93.0

# -----BEGIN PGP SIGNATURE-----
#
# iQIzBAABCgAdFiEE/jCAc0MNZY5toBt1AZCmbAoQ/E8FAmpotfgACgkQAZCmbAoQ
# /E+k0w//YSJ/ZflxM5Hr/5yoAtNFC4Yfs0/PSyv/eHmFF6Je5w+gSD1Mqbb5Gpjw
# aie1ZPHhBLjSIV0NEdaLE0dSwvyn8hGLvnAEPzILqYQLO+tmOnXXZPb+jRF1ZPbL
# wCIuGMJ1m05qK1ezVS5EBrQMfYqzwCeCXjfMxEOh+KPryKuThMumHhHlk9Y6RJqD
# VcD3ZBTFCOHrYc+0qVkTFU6fhN+rP/EFSoNspr83yjbV0eiN3iuPvETPunCv/39h
# NdgcGpqrFu6EKD8iMCR0NO+9bn3uoVdMS6sTKooeqaEMbcoiAF8oSzaDrYz1IDl6
# rXrA2dZG6om4hKgqb6dd8GNCZEPdrJcbp7UoHkBFiJnUUuUlj+pw1UrYnu5N6UB9
# slGauaIdpPHAZkI2P1+xcMxof/X8IOWwAWo9Ijbm1KnyV1uwmPm+V/O+nS4zhqxN
# JJc2Uy2qNs3DtXF+g4Gs4U0VR9wyEJXPg983HisXUsZGi04okBNI41LAtvLE+4y7
# vlHHuSzrn2Vw3rzIoi/vqPwVO+JCM5BrRbKrvojp0sSBQ5tfqeTdwiUUKLxiF1zF
# A2go6M0w/l45S8hy+euf6vnJC8fc6F/LjZcC7GnDHQOFcTuUHfZoAYQIGWcFXqeC
# //D6KlJrK2mU7whe1frQLVuOEBiKNVmMl2R+amG+yJWI4hppcms=
# =jRO+
# -----END PGP SIGNATURE-----
# gpg: directory '/home/runner/.gnupg' created
# gpg: keybox '/home/runner/.gnupg/pubring.kbx' created
# gpg: Signature made Tue Jul 28 14:00:24 2026 UTC
# gpg:                using RSA key FE308073430D658E6DA01B750190A66C0A10FC4F
# gpg: Can't check signature: No public key
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@simonpasquier

Copy link
Copy Markdown

/hold

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 29, 2026
@simonpasquier

Copy link
Copy Markdown

requires openshift/cluster-monitoring-operator#3010
/approve
/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 30, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@simonpasquier: This PR has been marked as verified by CI.

Details

In response to this:

requires openshift/cluster-monitoring-operator#3010
/approve
/verified by CI

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 openshift-eng/jira-lifecycle-plugin repository.

@simonpasquier simonpasquier changed the title [bot] Bump openshift/prometheus-operator to v0.93.0 NO-ISSUE: [bot] Bump openshift/prometheus-operator to v0.93.0 Jul 30, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 30, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@openshift-monitoring-bot[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

Description

This is an automated version bump from CI.
The logs for this run can be found in the syncbot repo actions.

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 openshift-eng/jira-lifecycle-plugin repository.

@simonpasquier

Copy link
Copy Markdown

/retest-required

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 30, 2026
@openshift-monitoring-bot openshift-monitoring-bot Bot changed the title NO-ISSUE: [bot] Bump openshift/prometheus-operator to v0.93.0 [bot] Bump openshift/prometheus-operator to v0.93.0 Jul 31, 2026
@simonpasquier simonpasquier changed the title [bot] Bump openshift/prometheus-operator to v0.93.0 NO-ISSUE: [bot] Bump openshift/prometheus-operator to v0.93.0 Aug 3, 2026
@simonpasquier

Copy link
Copy Markdown

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 3, 2026
@openshift-merge-bot

Copy link
Copy Markdown

Scheduling required tests:
/test e2e-agnostic-cmo
/test e2e-aws
/test e2e-aws-upgrade

@openshift-ci

openshift-ci Bot commented Aug 3, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-monitoring-bot[bot], simonpasquier

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@simonpasquier

Copy link
Copy Markdown

/hold cancel
/test e2e-agnostic-cmo

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 3, 2026
@simonpasquier

Copy link
Copy Markdown

/test e2e-agnostic-cmo

@openshift-ci

openshift-ci Bot commented Aug 3, 2026

Copy link
Copy Markdown

@openshift-monitoring-bot[bot]: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@openshift-merge-bot
openshift-merge-bot Bot merged commit 49894fa into openshift:main Aug 3, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.