AGENT-1522: Graduate InternalReleaseImage from v1alpha1 to v1 by pawanpinjarkar · Pull Request #2880 · openshift/api

pawanpinjarkar · 2026-06-08T19:55:40Z

Created machineconfiguration/v1/types_internalreleaseimage.go with v1 API
Updated compatibility level from 4 (alpha) to 1 (stable/GA)
Registered InternalReleaseImage types in v1 scheme
Created v1 integration test suite
Updated payload CRD script to use v1 instead of v1alpha1
Generated all CRD manifests, deepcopy, and swagger docs

Original PR from @sadasu #2863

openshift-ci-robot · 2026-06-08T19:55:44Z

@pawanpinjarkar: This pull request references AGENT-1522 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:

Created machineconfiguration/v1/types_internalreleaseimage.go with v1 API
Updated compatibility level from 4 (alpha) to 1 (stable/GA)
Registered InternalReleaseImage types in v1 scheme
Created v1 integration test suite
Updated payload CRD script to use v1 instead of v1alpha1
Generated all CRD manifests, deepcopy, and swagger docs
Original PR from @sadasu #2863

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 · 2026-06-08T19:55:48Z

Hello @pawanpinjarkar! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

openshift-merge-bot · 2026-06-08T19:55:53Z

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

coderabbitai · 2026-06-08T19:55:54Z

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

📝 Walkthrough

Walkthrough

This pull request introduces the InternalReleaseImage cluster-scoped singleton API: new Go types and validation markers, registration of InternalReleaseImage and InternalReleaseImageList with the machineconfiguration v1 scheme, updated generated CRD payloads to publish v1 schema text and tightened status validation, a YAML test suite covering create/update validation and reconciliation scenarios, and a change to hack/update-payload-crds.sh removing the old v1alpha1 internalreleaseimages glob.

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically summarizes the main change: graduating InternalReleaseImage from v1alpha1 to v1, which is the primary objective reflected throughout the changeset.
Description check	✅ Passed	The description is directly related to the changeset, listing the key modifications including the v1 types file, compatibility level update, scheme registration, test suite, CRD script updates, and generated artifacts.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
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.
Stable And Deterministic Test Names	✅ Passed	All test names in the added test file are stable and deterministic. The 10 test cases use purely descriptive static strings with no dynamic content like timestamps, UUIDs, or generated identifiers.
Test Structure And Quality	✅ Passed	Test file follows Ginkgo quality patterns: (1) Single responsibility: each test validates one behavior - onCreate tests focus on spec validation, onUpdate tests validate controller behavior (spec→s...
Microshift Test Compatibility	✅ Passed	No Ginkgo e2e tests were added in this PR. The test file added is a YAML manifest structure for CRD validation, not a Ginkgo test file. The check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	No Ginkgo e2e tests were added in this PR. The PR adds Go API type definitions, registration code, and YAML CRD validation test manifests, but not e2e test code. The check does not apply.
Topology-Aware Scheduling Compatibility	✅ Passed	PR only contains API type definitions, CRD schemas, and tests—no deployment manifests, operator code, or controllers with scheduling constraints. Topology-aware scheduling check is not applicable.
Ote Binary Stdout Contract	✅ Passed	PR modifies only API type definitions, scheme registration, test manifests, and CRD files. No process-level code (main, init, TestMain, suite setup) with stdout writes found.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No Ginkgo e2e tests (It(), Describe(), Context(), etc.) were added. The PR only adds Go API types and a YAML CRD test fixture, not e2e tests.
No-Weak-Crypto	✅ Passed	No weak crypto, custom crypto implementations, or insecure comparison patterns found. PR contains API schema definitions and test fixtures with no cryptographic code.
Container-Privileges	✅ Passed	None of the PR changes involve container/K8s manifests with privilege escalation. Files contain API type definitions, CRD schemas, and build scripts with no privileged, hostPID, hostNetwork, hostIP...
No-Sensitive-Data-In-Logs	✅ Passed	The PR adds type definitions, CRD manifests, and test fixtures with no logging statements or sensitive data exposure (no passwords, tokens, API keys, PII, or internal hostnames logged).

_{✏️ 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.}

coderabbitai

Actionable comments posted: 3

🧹 Nitpick comments (1)

machineconfiguration/v1/tests/internalreleaseimages.machineconfiguration.openshift.io/NoRegistryClusterInstall.yaml (1)

1-307: ⚡ Quick win

Consider adding test for singleton name constraint.

The CRD has a validation rule enforcing metadata.name == 'cluster', but there's no onCreate test verifying that a different name (e.g., metadata.name: not-cluster) is properly rejected. This would help ensure the singleton constraint is working correctly.

📋 Suggested test case

Add this test case to the onCreate section:

 - name: Should reject non-cluster name (singleton constraint)initial: | apiVersion: machineconfiguration.openshift.io/v1 kind: InternalReleaseImage metadata: name: not-cluster spec: releases: - name: ocp-release-bundle-4.18.0-x86_64expectedError: "internalreleaseimage is a singleton, .metadata.name must be 'cluster'"

🤖 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
`@machineconfiguration/v1/tests/internalreleaseimages.machineconfiguration.openshift.io/NoRegistryClusterInstall.yaml`
around lines 1 - 307, Add an onCreate test to verify the singleton name
constraint for InternalReleaseImage: in the onCreate array add a test (e.g.,
name "Should reject non-cluster name (singleton constraint)") that creates an
InternalReleaseImage with metadata.name: not-cluster and a minimal spec.releases
entry, and set expectedError to the singleton rejection message (e.g.,
"internalreleaseimage is a singleton, .metadata.name must be 'cluster'"). Locate
the block handling onCreate tests and the InternalReleaseImage test entries
(symbols: onCreate, InternalReleaseImage, metadata.name, spec.releases) and
ensure the new test follows the same YAML structure as the other onCreate cases.

🤖 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 `@machineconfiguration/v1/types_internalreleaseimage.go`:
- Around line 19-24: The type comment for InternalReleaseImage lacks
documentation that this is a cluster-scoped singleton; update the top-of-file
doc comment for InternalReleaseImage to state that only one instance is allowed
and its metadata.name must equal "cluster" (i.e., singleton resource enforced by
validation metadata.name == 'cluster'), and mention it is cluster-scoped so
consumers understand it represents a single cluster-wide configuration.
- Around line 103-120: Update the comment for the Conditions field to document
the MinItems/MaxItems validation and optionality: state that when the optional
Conditions slice is present it must contain between 1 and 5 metav1.Condition
entries (inclusive) corresponding to the allowed types (Mounted, Installing,
Available, Removing, Degraded), but the entire field may be omitted when no
status is available; ensure this text is added right above the Conditions
[]metav1.Condition `json:"conditions,omitempty"` declaration so reviewers can
see the +kubebuilder:validation:MinItems=1 and
+kubebuilder:validation:MaxItems=5 constraints are documented.
- Around line 70-78: Update the comment for the Conditions field on the
InternalReleaseImage type to document the +kubebuilder:validation:MinItems=1 and
+kubebuilder:validation:MaxItems=20 constraints and clarify the +optional
behavior: state that the field may be omitted entirely, but if present it must
contain between 1 and 20 metav1.Condition entries (valid types: Degraded), and
note the listType=map/listMapKey behavior as already described; edit the comment
immediately above the Conditions []metav1.Condition declaration to include this
text so reviewers can see the validation rules and optionality.
---
Nitpick comments:
In
`@machineconfiguration/v1/tests/internalreleaseimages.machineconfiguration.openshift.io/NoRegistryClusterInstall.yaml`:
- Around line 1-307: Add an onCreate test to verify the singleton name
constraint for InternalReleaseImage: in the onCreate array add a test (e.g.,
name "Should reject non-cluster name (singleton constraint)") that creates an
InternalReleaseImage with metadata.name: not-cluster and a minimal spec.releases
entry, and set expectedError to the singleton rejection message (e.g.,
"internalreleaseimage is a singleton, .metadata.name must be 'cluster'"). Locate
the block handling onCreate tests and the InternalReleaseImage test entries
(symbols: onCreate, InternalReleaseImage, metadata.name, spec.releases) and
ensure the new test follows the same YAML structure as the other onCreate cases.

🪄 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), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 662c10ce-ee1a-4b46-8b2b-217c2756384d

📥 Commits

Reviewing files that changed from the base of the PR and between 1194f4c and 582270b.

⛔ Files ignored due to path filters (6)

machineconfiguration/v1/zz_generated.crd-manifests/0000_80_machine-config_01_internalreleaseimages-Hypershift.crd.yaml is excluded by !**/zz_generated.crd-manifests/*
machineconfiguration/v1/zz_generated.crd-manifests/0000_80_machine-config_01_internalreleaseimages-SelfManagedHA.crd.yaml is excluded by !**/zz_generated.crd-manifests/*
machineconfiguration/v1/zz_generated.deepcopy.go is excluded by !**/zz_generated*
machineconfiguration/v1/zz_generated.featuregated-crd-manifests.yaml is excluded by !**/zz_generated*
machineconfiguration/v1/zz_generated.featuregated-crd-manifests/internalreleaseimages.machineconfiguration.openshift.io/NoRegistryClusterInstall.yaml is excluded by !**/zz_generated.featuregated-crd-manifests/**
machineconfiguration/v1/zz_generated.swagger_doc_generated.go is excluded by !**/zz_generated*

📒 Files selected for processing (6)

hack/update-payload-crds.sh
machineconfiguration/v1/register.go
machineconfiguration/v1/tests/internalreleaseimages.machineconfiguration.openshift.io/NoRegistryClusterInstall.yaml
machineconfiguration/v1/types_internalreleaseimage.go
payload-manifests/crds/0000_80_machine-config_01_internalreleaseimages-Hypershift.crd.yaml
payload-manifests/crds/0000_80_machine-config_01_internalreleaseimages-SelfManagedHA.crd.yaml

💤 Files with no reviewable changes (1)

hack/update-payload-crds.sh

pawanpinjarkar · 2026-06-09T00:10:38Z

/assign @yuqi-zhang

andfasano · 2026-06-09T07:23:12Z

/lgtm

Note for the reviewers: this is required for the NoRegistryClusterInstall feature promotion, see #2859

openshift-merge-bot · 2026-06-09T07:23:59Z

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial-1of2
/test e2e-aws-serial-2of2
/test e2e-aws-serial-techpreview-1of2
/test e2e-aws-serial-techpreview-2of2
/test e2e-azure
/test e2e-gcp
/test e2e-upgrade
/test e2e-upgrade-out-of-change
/test minor-e2e-upgrade-minor

pawanpinjarkar · 2026-06-09T13:08:22Z

/retest-required

pawanpinjarkar · 2026-06-09T14:43:40Z

/verified later @pawanpinjarkar

openshift-ci-robot · 2026-06-09T14:43:54Z

@pawanpinjarkar: This PR has been marked to be verified later by @pawanpinjarkar.

Details

In response to this:

/verified later @pawanpinjarkar

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.

pawanpinjarkar · 2026-06-09T23:11:49Z

/retest-required

yuqi-zhang · 2026-06-10T00:47:11Z

/verified later @pawanpinjarkar

For this PR I would say let's verify through CI directly. Like what we did for openshift/machine-config-operator#6076 (comment) . We can't merge this by itself, and we shouldn't merge without proving all the component pieces work together with an overall switch

The overall API itself looks mostly good, just some minor cleanup needed

openshift-ci-robot · 2026-06-10T00:47:21Z

@yuqi-zhang: This PR has been marked to be verified later by @pawanpinjarkar.

Details

In response to this:

/verified later @pawanpinjarkar
For this PR I would say let's verify through CI directly. Like what we did for openshift/machine-config-operator#6076 (comment) . We can't merge this by itself, and we shouldn't merge without proving all the component pieces work together with an overall switch

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.

yuqi-zhang · 2026-06-10T00:50:45Z

+	// conditions represent the observations of an internal release image current state. Valid types are:
+	// Mounted, Installing, Available, Removing and Degraded.
+	//
+	// If Mounted is true, that means that a valid ISO has been discovered and mounted on one of the cluster nodes.


Just a question, can multiple conditions be true at the same time? Or can only 1 be true at a time?

Potentially there could be more conditions true simultaneously. For example, Mounted will be set to True when the ISO will be discovered, and if the user decides to add its content (by editing the IRI resource) also Installing will become true

yuqi-zhang · 2026-06-10T00:51:27Z

/verified cancel

openshift-ci-robot · 2026-06-10T00:51:30Z

@yuqi-zhang: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

/verified cancel

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.

yuqi-zhang · 2026-06-10T00:51:53Z

/verified remove

andfasano · 2026-07-02T06:59:01Z

/retest-required

andfasano · 2026-07-02T08:14:36Z

/lgtm

openshift-merge-bot · 2026-07-02T08:15:03Z

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial-1of2
/test e2e-aws-serial-2of2
/test e2e-aws-serial-techpreview-1of2
/test e2e-aws-serial-techpreview-2of2
/test e2e-azure
/test e2e-gcp
/test e2e-upgrade
/test e2e-upgrade-out-of-change
/test minor-e2e-upgrade-minor

openshift-ci · 2026-07-02T08:15:07Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andfasano, bfournie, everettraven

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~~ [everettraven]

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

andfasano · 2026-07-02T10:17:58Z

/test minor-e2e-upgrade-minor

andfasano · 2026-07-02T10:30:39Z

/test minor-e2e-upgrade-minor

This job seems to have some issue

pawanpinjarkar · 2026-07-02T13:40:52Z

/verified later

openshift-ci-robot · 2026-07-02T13:40:54Z

@pawanpinjarkar: /verified later <@username> requires at least one GitHub @username to be specified (it can be a comma delimited list). It indicates the engineer(s) that will be performing the verification. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

/verified later

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.

pawanpinjarkar · 2026-07-02T13:42:16Z

/verified later @pawanpinjarkar

pawanpinjarkar · 2026-07-02T13:42:32Z

/retest-required

openshift-ci-robot · 2026-07-02T13:42:38Z

@pawanpinjarkar: This PR has been marked to be verified later by @pawanpinjarkar.

Details

In response to this:

/verified later @pawanpinjarkar

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.

pawanpinjarkar · 2026-07-02T16:36:23Z

/hold cancel

andfasano · 2026-07-02T17:24:01Z

/test e2e-aws-ovn-hypershift

openshift-merge-bot · 2026-07-02T17:24:11Z

/retest-required

Remaining retests: 0 against base HEAD b56324c and 2 for PR HEAD 02030eb in total

openshift-ci · 2026-07-02T20:20:48Z

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

pawanpinjarkar · 2026-07-13T15:46:13Z

/cherrypick release-4.22

openshift-cherrypick-robot · 2026-07-13T15:47:18Z

@pawanpinjarkar: #2880 failed to apply on top of branch "release-4.22":

Applying: AGENT-1522: Graduate InternalReleaseImage from v1alpha1 to v1
.git/rebase-apply/patch:385: trailing whitespace.
// This is a singleton resource with 'cluster' as the only valid name. warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	hack/update-payload-crds.sh
M	machineconfiguration/v1/register.go
M	machineconfiguration/v1/zz_generated.deepcopy.go
M	machineconfiguration/v1/zz_generated.featuregated-crd-manifests.yaml
M	machineconfiguration/v1/zz_generated.swagger_doc_generated.go
Falling back to patching base and 3-way merge...
Auto-merging hack/update-payload-crds.sh
CONFLICT (content): Merge conflict in hack/update-payload-crds.sh
Auto-merging machineconfiguration/v1/register.go
Auto-merging machineconfiguration/v1/zz_generated.deepcopy.go
Auto-merging machineconfiguration/v1/zz_generated.featuregated-crd-manifests.yaml
Auto-merging machineconfiguration/v1/zz_generated.swagger_doc_generated.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 AGENT-1522: Graduate InternalReleaseImage from v1alpha1 to v1

Details

In response to this:

/cherrypick release-4.22

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.

Add manual CRD override to include v1alpha1 schema alongside v1 schema for InternalReleaseImage API. This allows both API versions to coexist during the graduation period, enabling gradual migration from v1alpha1 to v1 across dependent repositories. The manual override contains the complete v1alpha1 schema from the featuregated manifest, which will be merged with the v1 schema during code generation to produce a CRD that serves both versions. This addresses the review feedback to support both schemas simultaneously rather than requiring all consumers to update at once. Related: #2880 (comment)

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

openshift-ciBot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Jun 8, 2026

openshift-ciBot requested review from everettraven and yuqi-zhang June 8, 2026 19:56

coderabbitaiBot reviewed Jun 8, 2026
View reviewed changes

Comment threadmachineconfiguration/v1/types_internalreleaseimage.go
Comment threadmachineconfiguration/v1/types_internalreleaseimage.go
Comment threadmachineconfiguration/v1/types_internalreleaseimage.go

pawanpinjarkar mentioned this pull request Jun 9, 2026
AGENT-1522: Graduate IRI object from v1alpha1 to V1 #2863
Closed

openshift-ciBot assigned yuqi-zhang Jun 9, 2026

pawanpinjarkar force-pushed the pr-2863-branch branch from 21badc0 to 31e0df0Compare June 9, 2026 00:12

openshift-ciBot assigned andfasano Jun 9, 2026

openshift-ciBot added the lgtm Indicates that a PR is ready to be merged. label Jun 9, 2026

openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Jun 9, 2026

yuqi-zhang reviewed Jun 10, 2026
View reviewed changes

openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Jun 10, 2026

openshift-ciBot requested review from bfournie and sadasu July 1, 2026 18:01

pawanpinjarkar requested a review from yuqi-zhang July 1, 2026 18:04

pawanpinjarkar added 2 commits July 1, 2026 16:52

Fix integration test
483b3d0

Fix Typo
02030eb

openshift-ciBot added the lgtm Indicates that a PR is ready to be merged. label Jul 2, 2026

openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Jul 2, 2026

openshift-ciBot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 2, 2026

openshift-merge-botBot merged commit ef71f94 into openshift:masterJul 2, 2026
29 checks passed

pawanpinjarkar mentioned this pull request Jul 7, 2026
AGENT-1493: Promote NoRegistryClusterInstall Feature to Default #2859
Merged

pawanpinjarkar mentioned this pull request Jul 13, 2026
[release-4.22] AGENT-1544: Backport NoRegistryClusterInstall feature to release-4.22 #2930
Merged

Uh oh!

Conversation

pawanpinjarkar commented Jun 8, 2026

Uh oh!

openshift-ci-robot commented Jun 8, 2026• edited by openshift-ci BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ciBot commented Jun 8, 2026

Uh oh!

openshift-merge-botBot commented Jun 8, 2026

Uh oh!

coderabbitaiBot commented Jun 8, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviews paused

Walkthrough

Uh oh!

coderabbitaiBot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

pawanpinjarkar commented Jun 9, 2026

Uh oh!

andfasano commented Jun 9, 2026

Uh oh!

openshift-merge-botBot commented Jun 9, 2026

Uh oh!

pawanpinjarkar commented Jun 9, 2026

Uh oh!

pawanpinjarkar commented Jun 9, 2026

Uh oh!

openshift-ci-robot commented Jun 9, 2026

Uh oh!

pawanpinjarkar commented Jun 9, 2026

Uh oh!

yuqi-zhang commented Jun 10, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Jun 10, 2026

Uh oh!

yuqi-zhangJun 10, 2026

Choose a reason for hiding this comment

Uh oh!

andfasanoJun 10, 2026

Choose a reason for hiding this comment

Uh oh!

yuqi-zhang commented Jun 10, 2026

Uh oh!

openshift-ci-robot commented Jun 10, 2026

Uh oh!

yuqi-zhang commented Jun 10, 2026

Uh oh!

andfasano commented Jul 2, 2026

Uh oh!

andfasano commented Jul 2, 2026

Uh oh!

openshift-merge-botBot commented Jul 2, 2026

Uh oh!

openshift-ciBot commented Jul 2, 2026

Uh oh!

andfasano commented Jul 2, 2026

Uh oh!

andfasano commented Jul 2, 2026

Uh oh!

pawanpinjarkar commented Jul 2, 2026

Uh oh!

openshift-ci-robot commented Jul 2, 2026

Uh oh!

pawanpinjarkar commented Jul 2, 2026

Uh oh!

pawanpinjarkar commented Jul 2, 2026

Uh oh!

openshift-ci-robot commented Jul 2, 2026

Uh oh!

pawanpinjarkar commented Jul 2, 2026

Uh oh!

andfasano commented Jul 2, 2026

Uh oh!

openshift-merge-botBot commented Jul 2, 2026

openshift-ci-robot commented Jun 8, 2026•
edited by openshift-ci Bot
Loading

coderabbitaiBot commented Jun 8, 2026•
edited
Loading

yuqi-zhang commented Jun 10, 2026•
edited
Loading