Skip to content

chore: update [obo-]prometheus-operator to v0.91.0#1096

Merged
openshift-merge-bot[bot] merged 1 commit into
rhobs:mainfrom
jan--f:bump-p-o-0.91
May 21, 2026
Merged

chore: update [obo-]prometheus-operator to v0.91.0#1096
openshift-merge-bot[bot] merged 1 commit into
rhobs:mainfrom
jan--f:bump-p-o-0.91

Conversation

@jan--f
Copy link
Copy Markdown
Collaborator

@jan--f jan--f commented May 21, 2026

No description provided.

Signed-off-by: Jan Fajerski <jfajersk@redhat.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 21, 2026

Review Change Stack

📝 Walkthrough

Walkthrough

This PR upgrades the observability operator to Prometheus Operator 0.91.0-rhobs1 (from 0.90.1-rhobs1). The changes include version bumps across CRD manifests, deployment definitions, and Go dependencies, plus schema extensions: AWS SigV4 externalId field with validation, email threading support, Mattermost webhook configuration, Prometheus sharding strategy with distributed target assignment, TLS cipher/curve options, and ScrapeConfig constraint improvements including mutual exclusivity validation and string length constraints.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive No description was provided by the author, making it impossible to assess whether the description relates to the changeset. Add a pull request description explaining the update purpose, testing performed, and any breaking changes or migration notes.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: updating prometheus-operator dependencies from v0.90.1 to v0.91.0 across manifests and configuration files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.12.2)

Error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions
The command is terminated due to an error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@bundle/manifests/monitoring.rhobs_prometheusagents.yaml`:
- Around line 7781-7794: The current validation only ensures topology exists
when mode == 'Topology' but doesn't require topology.values to be present and
non-empty; update the x-kubernetes-validations for the shardingStrategy (the
rule that references self.mode and self.topology) to also require that
self.topology.values exists and has at least one element when self.mode ==
'Topology' (e.g. extend the rule to '!has(self.topology) || (has(self.mode) &&
self.mode == ''Topology'' && has(self.topology.values) &&
size(self.topology.values) > 0)') so mode=Topology is invalid unless
topology.values is set and non-empty.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: dab62113-1aeb-4057-b53e-0465179c060d

📥 Commits

Reviewing files that changed from the base of the PR and between d0bde27 and 5638e72.

⛔ Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
📒 Files selected for processing (16)
  • bundle/manifests/monitoring.rhobs_alertmanagerconfigs.yaml
  • bundle/manifests/monitoring.rhobs_alertmanagers.yaml
  • bundle/manifests/monitoring.rhobs_podmonitors.yaml
  • bundle/manifests/monitoring.rhobs_probes.yaml
  • bundle/manifests/monitoring.rhobs_prometheusagents.yaml
  • bundle/manifests/monitoring.rhobs_prometheuses.yaml
  • bundle/manifests/monitoring.rhobs_prometheusrules.yaml
  • bundle/manifests/monitoring.rhobs_scrapeconfigs.yaml
  • bundle/manifests/monitoring.rhobs_servicemonitors.yaml
  • bundle/manifests/monitoring.rhobs_thanosrulers.yaml
  • bundle/manifests/obo-prometheus-operator-admission-webhook_policy_v1_poddisruptionbudget.yaml
  • bundle/manifests/obo-prometheus-operator-admission-webhook_v1_service.yaml
  • bundle/manifests/obo-prometheus-operator_v1_service.yaml
  • bundle/manifests/observability-operator.clusterserviceversion.yaml
  • deploy/dependencies/kustomization.yaml
  • go.mod

Comment on lines +7781 to +7794
values:
description: |-
values defines the list of topology values (e.g. zone names) to be used
for sharding. The configured number of shards must be greater than or
equal to the number of values.
items:
type: string
type: array
x-kubernetes-list-type: atomic
type: object
type: object
x-kubernetes-validations:
- message: topology can only be defined when mode is set to 'Topology'
rule: '!has(self.topology) || (has(self.mode) && self.mode == ''Topology'')'
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Require topology.values when mode is Topology.

As written, shardingStrategy.mode: Topology is still valid if topology is missing or topology.values is empty. That admits a config with no zones to assign, and the Line 11372 shard-count rule never fires in that case.

Suggested validation tightening
               x-kubernetes-validations:
               - message: topology can only be defined when mode is set to 'Topology'
                 rule: '!has(self.topology) || (has(self.mode) && self.mode == ''Topology'')'
+              - message: topology.values must be non-empty when mode is set to 'Topology'
+                rule: '!has(self.mode) || self.mode != ''Topology'' || (has(self.topology) && has(self.topology.values) && self.topology.values.size() > 0)'
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@bundle/manifests/monitoring.rhobs_prometheusagents.yaml` around lines 7781 -
7794, The current validation only ensures topology exists when mode ==
'Topology' but doesn't require topology.values to be present and non-empty;
update the x-kubernetes-validations for the shardingStrategy (the rule that
references self.mode and self.topology) to also require that
self.topology.values exists and has at least one element when self.mode ==
'Topology' (e.g. extend the rule to '!has(self.topology) || (has(self.mode) &&
self.mode == ''Topology'' && has(self.topology.values) &&
size(self.topology.values) > 0)') so mode=Topology is invalid unless
topology.values is set and non-empty.

Copy link
Copy Markdown
Contributor

@simonpasquier simonpasquier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 21, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jan--f, 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:
  • OWNERS [jan--f,simonpasquier]

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

@openshift-merge-bot openshift-merge-bot Bot merged commit a9ee117 into rhobs:main May 21, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants