OTA-1956: ci-operator/config/openshift/cluster-update-console-plugin: Promote to CI releases by wking · Pull Request #77945 · openshift/release

wking · 2026-04-16T22:22:33Z

Bulding on #77093, the goal is to include the plugin in 5.0 OpenShift releases in a similar way to how
ci-operator/config/openshift/monitoring-plugin/openshift-monitoring-plugin-main.yaml already works, so just clone that portion of their config. Docs here and here.

Summary by CodeRabbit

Chores
- Switched CI to an integration-style latest release that includes built images and promotes a named release as the latest.
- Added explicit image build inputs and a publish/promotion target so pipeline-built images are produced and published.
- Adjusted presubmits: removed an outdated release label from the frontend presubmit and added a presubmit that always runs image builds and supports manual reruns.
- Added a postsubmit promotion job to run image builds and publish artifacts after merges.

openshift-ci-robot · 2026-04-16T22:22:37Z

@wking: This pull request references OTA-1956 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Bulding on #77093, the goal is to include the plugin in 5.0 OpenShift releases in a similar way to how
ci-operator/config/openshift/monitoring-plugin/openshift-monitoring-plugin-main.yaml already works, so just clone that portion of their config. Docs here and here.

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.

wking · 2026-04-16T22:26:22Z

/pj-rehearse auto-ack

openshift-merge-bot · 2026-04-16T22:26:26Z

@wking: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

coderabbitai · 2026-04-16T22:26:29Z

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 1dd08c71-1c6c-4252-9607-c8c75ff36007

📥 Commits

Reviewing files that changed from the base of the PR and between e173b21 and ba3fb7d.

📒 Files selected for processing (3)

ci-operator/config/openshift/cluster-update-console-plugin/openshift-cluster-update-console-plugin-main.yaml
ci-operator/jobs/openshift/cluster-update-console-plugin/openshift-cluster-update-console-plugin-main-postsubmits.yaml
ci-operator/jobs/openshift/cluster-update-console-plugin/openshift-cluster-update-console-plugin-main-presubmits.yaml

✅ Files skipped from review due to trivial changes (1)

ci-operator/jobs/openshift/cluster-update-console-plugin/openshift-cluster-update-console-plugin-main-postsubmits.yaml

🚧 Files skipped from review as they are similar to previous changes (1)

ci-operator/config/openshift/cluster-update-console-plugin/openshift-cluster-update-console-plugin-main.yaml

Walkthrough

Switched the release target from a candidate to an integration release (named/namespaced, including built images), added a Dockerfile-based image build and explicit promotion target, removed a presubmit job-release label, added an images presubmit, and added a postsubmit promotion job for images.

Changes

Cohort / File(s)	Summary
Release / Image config `ci-operator/config/openshift/cluster-update-console-plugin/openshift-cluster-update-console-plugin-main.yaml`	Added `images.items` with a Dockerfile build (`dockerfile_path: Dockerfile`, `to: cluster-update-console-plugin`). Replaced `releases.latest.candidate` with `releases.latest.integration` (`include_built_images: true`, `identity: name: "5.0", namespace: ocp`). Added `promotion.to: name: "5.0", namespace: ocp`.
Presubmit jobs `ci-operator/jobs/openshift/cluster-update-console-plugin/openshift-cluster-update-console-plugin-main-presubmits.yaml`	Removed `labels.job-release: "4.22"` from the frontend presubmit. Added `pull-ci-openshift-cluster-update-console-plugin-main-images` presubmit: runs on `^main$`/`^main-`, `always_run: true`, `cluster: build11`, `context: ci/prow/images`, decorated, labeled `ci.openshift.io/generator: prowgen` and `pj-rehearse.openshift.io/can-be-rehearsed: "true"`, `rerun_command: /test images`, trigger for `/test ... images`, runs `ci-operator` with `--target=[images]` and `--target=[release:latest]`, mounts secrets (`gcs-credentials`, `manifest-tool-local-pusher`, `pull-secret`, `result-aggregator`), `serviceAccountName: ci-operator`.
Postsubmit jobs `ci-operator/jobs/openshift/cluster-update-console-plugin/openshift-cluster-update-console-plugin-main-postsubmits.yaml`	Added a new postsubmit `branch-ci-openshift-cluster-update-console-plugin-main-images` that runs on `^main$`, `kubernetes` agent, `always_run: true`, `decorate: true`, `cluster: build01`, `max_concurrency: 1`, labeled as a promotion job, runs `ci-operator` container targeting `[images]` with args for GCS upload, image import/push, promotion and credentials reporting, mounts required secrets, and uses `serviceAccountName: ci-operator`.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 10

✅ Passed checks (10 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: promoting the cluster-update-console-plugin to CI releases (version 5.0), which is the primary objective reflected across all three modified files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Stable And Deterministic Test Names	✅ Passed	PR modifies only CI/CD configuration YAML files, not Ginkgo test code. Check not applicable.
Test Structure And Quality	✅ Passed	The PR exclusively modifies CI-operator configuration and Prow job definition YAML files, not Ginkgo test code. The custom check for Ginkgo test structure is not applicable to infrastructure configuration changes.
Microshift Test Compatibility	✅ Passed	This PR does not introduce any new Ginkgo e2e tests; changes are exclusively declarative CI/CD configuration files with no Ginkgo test patterns found.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR modifies only CI/CD configuration YAML files (ci-operator config and Prow job definitions), containing no new Ginkgo e2e test code.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies only CI/CD infrastructure configuration files (ci-operator build configs and Prow job definitions), not deployment manifests or operator code. No Kubernetes pod scheduling constraints, affinity rules, or topology spread constraints introduced.
Ote Binary Stdout Contract	✅ Passed	The OTE Binary Stdout Contract check is not applicable to this pull request. The PR exclusively modifies YAML configuration files with no associated Go source code or test binaries.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	This PR modifies only CI/operator configuration YAML files for cluster-update-console-plugin, not Ginkgo e2e test files.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

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

openshift-ci-robot · 2026-04-16T22:26:51Z

@wking: This pull request references OTA-1956 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Bulding on #77093, the goal is to include the plugin in 5.0 OpenShift releases in a similar way to how
ci-operator/config/openshift/monitoring-plugin/openshift-monitoring-plugin-main.yaml already works, so just clone that portion of their config. Docs here and here.

Summary by CodeRabbit

Chores

Updated CI/CD build and release configuration for the cluster update console plugin, including release parameters and build output definitions.

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.

openshift-ci-robot · 2026-04-16T22:30:52Z

@wking: This pull request references OTA-1956 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Bulding on #77093, the goal is to include the plugin in 5.0 OpenShift releases in a similar way to how
ci-operator/config/openshift/monitoring-plugin/openshift-monitoring-plugin-main.yaml already works, so just clone that portion of their config. Docs here and here.

Summary by CodeRabbit

Chores

Updated CI/CD release configuration to use an integration-based release, include built images, and promote a named release target as the latest.

Adjusted presubmit jobs: removed an old release label from the frontend presubmit and added a new presubmit that always runs image builds and supports manual rerun via test commands.

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.

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@ci-operator/jobs/openshift/cluster-update-console-plugin/openshift-cluster-update-console-plugin-main-presubmits.yaml`:
- Around line 65-69: The images job
pull-ci-openshift-cluster-update-console-plugin-main-images mounts
promotion-related secrets but lacks an explicit cluster assignment, risking
secret access failures; update that job definition
(pull-ci-openshift-cluster-update-console-plugin-main-images) to include the
same cluster setting used by the companion frontend job (cluster: build11) so
the job runs on the correct cluster with access to manifest-tool-local-pusher,
pull-secret, and result-aggregator secrets.

🪄 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: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 5a583b4a-00de-4722-878d-853db6917ec5

📥 Commits

Reviewing files that changed from the base of the PR and between 6768891 and f159303.

📒 Files selected for processing (2)

ci-operator/config/openshift/cluster-update-console-plugin/openshift-cluster-update-console-plugin-main.yaml
ci-operator/jobs/openshift/cluster-update-console-plugin/openshift-cluster-update-console-plugin-main-presubmits.yaml

🚧 Files skipped from review as they are similar to previous changes (1)

ci-operator/config/openshift/cluster-update-console-plugin/openshift-cluster-update-console-plugin-main.yaml

openshift-ci-robot · 2026-04-16T22:35:52Z

@wking: This pull request references OTA-1956 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Bulding on #77093, the goal is to include the plugin in 5.0 OpenShift releases in a similar way to how
ci-operator/config/openshift/monitoring-plugin/openshift-monitoring-plugin-main.yaml already works, so just clone that portion of their config. Docs here and here.

Summary by CodeRabbit

Chores

Updated CI/CD release configuration to switch to an integration-style release, include built images by default, and promote an explicitly named release as the latest.

Added explicit image build inputs and publishing target so built images are produced and published during pipelines.

Adjusted presubmit jobs: removed an outdated release label from the frontend presubmit and added a new presubmit that always runs image builds and supports manual reruns via test commands.

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.

openshift-ci-robot · 2026-04-16T23:13:29Z

@wking: This pull request references OTA-1956 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Bulding on #77093, the goal is to include the plugin in 5.0 OpenShift releases in a similar way to how
ci-operator/config/openshift/monitoring-plugin/openshift-monitoring-plugin-main.yaml already works, so just clone that portion of their config. Docs here and here.

Summary by CodeRabbit

Chores

Switched CI release config to an integration-style latest release, including built images and promoting a named release as the latest.

Added explicit image build inputs and a publish target so pipeline-built images are produced and published.

Adjusted presubmit jobs: removed an outdated release label from the frontend presubmit and added a new presubmit that always runs image builds and supports manual reruns via test commands.

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.

…o CI releases The goal is to include the plugin in 5.0 OpenShift releases in a similar way to how ci-operator/config/openshift/monitoring-plugin/openshift-monitoring-plugin-main.yaml already works, so just clone that portion of their config. Docs [1,2]. [1]: https://docs.ci.openshift.org/architecture/ci-operator/#publishing-to-an-integration-stream [2]: https://docs.ci.openshift.org/architecture/ci-operator/#testing-with-an-ephemeral-openshift-release

wking · 2026-04-16T23:27:38Z

/pj-rehearse auto-ack

openshift-merge-bot · 2026-04-16T23:27:41Z

@wking: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

openshift-ci-robot · 2026-04-16T23:28:28Z

@wking: This pull request references OTA-1956 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Bulding on #77093, the goal is to include the plugin in 5.0 OpenShift releases in a similar way to how
ci-operator/config/openshift/monitoring-plugin/openshift-monitoring-plugin-main.yaml already works, so just clone that portion of their config. Docs here and here.

Summary by CodeRabbit

Chores

Switched CI to an integration-style latest release that includes built images and promotes a named release as the latest.

Added explicit image build inputs and a publish/promotion target so pipeline-built images are produced and published.

Adjusted presubmits: removed an outdated release label from the frontend presubmit and added a presubmit that always runs image builds and supports manual reruns.

Added a postsubmit promotion job to run image builds and publish artifacts after merges.

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.

openshift-merge-bot · 2026-04-16T23:30:39Z

[REHEARSALNOTIFIER]
@wking: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-cluster-update-console-plugin-main-images	openshift/cluster-update-console-plugin	presubmit	Presubmit changed
pull-ci-openshift-cluster-update-console-plugin-main-frontend	openshift/cluster-update-console-plugin	presubmit	Ci-operator config changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

openshift-ci · 2026-04-17T10:18:27Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongkailiu, wking

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:

~~ci-operator/config/openshift/cluster-update-console-plugin/OWNERS~~ [hongkailiu,wking]
~~ci-operator/jobs/openshift/cluster-update-console-plugin/OWNERS~~ [hongkailiu,wking]

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

openshift-ci · 2026-04-17T10:51:57Z

@wking: 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.

…o CI releases (openshift#77945) The goal is to include the plugin in 5.0 OpenShift releases in a similar way to how ci-operator/config/openshift/monitoring-plugin/openshift-monitoring-plugin-main.yaml already works, so just clone that portion of their config. Docs [1,2]. [1]: https://docs.ci.openshift.org/architecture/ci-operator/#publishing-to-an-integration-stream [2]: https://docs.ci.openshift.org/architecture/ci-operator/#testing-with-an-ephemeral-openshift-release

The console folks are pushing to decentralize console implementation from [1], so we've created a new console plugin for cluster updates [2]. It's built by both CI [3] and ART [4]. Checking on app.ci ImageStreams: $ oc whoami -c default/api-ci-l2s4-p1-openshiftapps-com:6443/wking $ oc -n ocp get -o json imagestream 5.0 | jq -r '.status.tags[] | select(.tag == "cluster-update-console-plugin").items[] | .created + " " + .image' 2026-05-01T20:55:38Z sha256:10e4f1b5763f40372823173b2a9528777ff8e97d416c5447e10df023c0e35656 2026-04-29T05:00:56Z sha256:b0433455cbbff13bdda03ee78371e18c139adebc00432dea716e8cdf83eeb042 2026-04-17T11:10:31Z sha256:e1296b64ffb35757fb2fb56bb5dd9cbd55c7f17f9f59c0a10a2d71a0ad6702d3 $ oc -n ocp get -o json imagestream 5.0-art-latest | jq -r '.status.tags[] | select(.tag == "cluster-update-console-plugin").items[] | .created + " " + .image' 2026-05-12T19:45:33Z sha256:b943be0ae0eba97c27741d0184e99a77ea928749cc578ae7e17a8e5329652642 2026-05-12T14:42:55Z sha256:c29ba37ef5a426de5320d680d3fb58befc530274e6df4c32b4dc4fd0acaaaae0 2026-05-12T09:02:35Z sha256:901bc6aac1142fe1da2a756bb4d91ae8fe14b459ce2bf9904ceae6d2fc818fc2 2026-05-12T04:38:56Z sha256:1f4e8b200d97f82db1784b4d7fc9f0bd3ccaf2cc664fd5f0ff6b80485da16950 2026-05-11T22:54:34Z sha256:d369ca7c73d7a3abe159e9e6f5644f63e0b091f0b75f202773a023e91c7faaf6 This commit sets up an image-references file [5], so 'oc adm release new ...' knows that we'll want that image injected in the Deployment manifest. I'm using placeholder.url.oc.will.replace.this.example.org as part of my placeholder name. That's similar to the machine-config operator's use of placeholder.url.oc.will.replace.this.org [6], except that I'm using a subdomain of the reserved example.com [7], to avoid any possible confusion with an actually in-use domain. The new manifests are in run-level 50, which is the default, so they can roll out in parallel with other components to avoid slowing updates. The new manifests are tried to the Console capability [8] and the TechPreviewNoUpgrade feature set [9] (in the absence of a specific feature gate for this functionality). I'm just carrying the old exclude.release.openshift.io/internal-openshift-hosted annotation over from other CVO manifests. It predates cluster profiles [10], and I'm not sure anyone still uses it, but it seems like the CVO should be consistent about whether it matters or not anymore. Perhaps we can drop it from all CVO manifests in follow-up work. Otherwise these manifests are loosely based on my attempts to meld the plugin's Help chart templates [11] with existing CVO manifest conventions. [1]: https://github.com/openshift/console [2]: https://github.com/openshift/cluster-update-console-plugin [3]: openshift/release#77945 [4]: openshift-eng/ocp-build-data#10393 [5]: https://github.com/openshift/enhancements/blob/4f67eee19ad16f1d5e9e8a2622b708e2ea6d8e6a/dev-guide/cluster-version-operator/dev/operators.md#how-do-i-ensure-the-right-images-get-used-by-my-manifests [6]: https://github.com/openshift/machine-config-operator/blob/99cb8a46e6a31b2b72d6a8371c6cd4ee45393263/install/image-references#L10 [7]: https://www.rfc-editor.org/rfc/rfc6761#section-6.5 [8]: https://github.com/openshift/enhancements/blob/4f67eee19ad16f1d5e9e8a2622b708e2ea6d8e6a/enhancements/installer/component-selection.md#manifest-annotations [9]: https://github.com/openshift/enhancements/blob/4f67eee19ad16f1d5e9e8a2622b708e2ea6d8e6a/enhancements/update/cvo-techpreview-manifests.md#proposal [10]: https://github.com/openshift/enhancements/blob/4f67eee19ad16f1d5e9e8a2622b708e2ea6d8e6a/enhancements/update/ibm-public-cloud-support.md#cluster-version-operator-changes-for-beta [11]: https://github.com/openshift/cluster-update-console-plugin/tree/9778f4fc0c19e60cad55a45591a066b6b7a3cb12/charts/openshift-console-plugin/templates

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 16, 2026

openshift-ci Bot requested review from DavidHurta and hongkailiu April 16, 2026 22:23

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 16, 2026

wking force-pushed the promote-cluster-update-console-plugin branch from 6768891 to f159303 Compare April 16, 2026 22:29

coderabbitai Bot reviewed Apr 16, 2026

View reviewed changes

Comment thread ...t/cluster-update-console-plugin/openshift-cluster-update-console-plugin-main-presubmits.yaml

wking force-pushed the promote-cluster-update-console-plugin branch from f159303 to 3cd71e7 Compare April 16, 2026 22:34

wking force-pushed the promote-cluster-update-console-plugin branch from 3cd71e7 to e173b21 Compare April 16, 2026 23:12

wking force-pushed the promote-cluster-update-console-plugin branch from e173b21 to ba3fb7d Compare April 16, 2026 23:27

openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Apr 16, 2026

hongkailiu approved these changes Apr 17, 2026

View reviewed changes

openshift-ci Bot assigned hongkailiu Apr 17, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 17, 2026

openshift-merge-bot Bot merged commit 0368f89 into openshift:main Apr 17, 2026
18 checks passed

wking mentioned this pull request May 12, 2026

WIP: OTA-1956: install: Add a TechPreviewNoUpgrade cluster-update console plugin openshift/cluster-version-operator#1388

Open

Conversation

wking commented Apr 16, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

openshift-ci-robot commented Apr 16, 2026 • edited by atlassian Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

wking commented Apr 16, 2026

Uh oh!

openshift-merge-bot Bot commented Apr 16, 2026

Uh oh!

coderabbitai Bot commented Apr 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviews paused

Walkthrough

Changes

Estimated code review effort

Uh oh!

openshift-ci-robot commented Apr 16, 2026 • edited by atlassian Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

openshift-ci-robot commented Apr 16, 2026 • edited by atlassian Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

openshift-ci-robot commented Apr 16, 2026 • edited by atlassian Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

openshift-ci-robot commented Apr 16, 2026 • edited by atlassian Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

wking commented Apr 16, 2026

Uh oh!

openshift-merge-bot Bot commented Apr 16, 2026

Uh oh!

openshift-ci-robot commented Apr 16, 2026 • edited by atlassian Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

openshift-merge-bot Bot commented Apr 16, 2026

Uh oh!

openshift-ci Bot commented Apr 17, 2026

Uh oh!

openshift-ci Bot commented Apr 17, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

wking commented Apr 16, 2026 •

edited by coderabbitai Bot

Loading

openshift-ci-robot commented Apr 16, 2026 •

edited by atlassian Bot

Loading

coderabbitai Bot commented Apr 16, 2026 •

edited

Loading

openshift-ci-robot commented Apr 16, 2026 •

edited by atlassian Bot

Loading

openshift-ci-robot commented Apr 16, 2026 •

edited by atlassian Bot

Loading

openshift-ci-robot commented Apr 16, 2026 •

edited by atlassian Bot

Loading

openshift-ci-robot commented Apr 16, 2026 •

edited by atlassian Bot

Loading

openshift-ci-robot commented Apr 16, 2026 •

edited by atlassian Bot

Loading