NO-JIRA: enable multi-architecture yarn builds by lgarciaaco · Pull Request #16228 · openshift/console

lgarciaaco · 2026-03-31T11:34:33Z

Summary

Enable multi-architecture yarn builds with hermetic build support

Changes

Convert Dockerfile to use hermetic build approach with cachi2 and add support for multiple architectures (x64, arm64, s390x, ppc64) in yarn configuration. This resolves hermetic build failures on non-x86_64 architectures by ensuring all required architecture-specific packages are included in dependency resolution.

Summary by CodeRabbit

Chores
- Streamlined frontend build pipeline for improved maintainability
- Extended platform architecture support for Linux deployments (x64, arm64, s390x, ppc64)

coderabbitai · 2026-03-31T11:38:12Z

📝 Walkthrough

Walkthrough

The Dockerfile's frontend build stage has been simplified by removing Corepack bootstrap logic and cachito-backed artifact handling in favor of direct Yarn invocation (yarn-4.12.0.cjs). A WORKDIR frontend directive was added, and subsequent build commands now execute relative to that directory. The frontend/.yarnrc.yml configuration file now declares supported architectures (linux on x64, arm64, s390x, and ppc64). The Cypress binary suppression setting was retained.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

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

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 `@Dockerfile`:
- Line 18: The Dockerfile uses a relative WORKDIR ("WORKDIR frontend") which is
brittle; replace that WORKDIR instruction with an absolute path instead so the
build is explicit and not dependent on the base image's CWD—update the WORKDIR
line in the Dockerfile (the "WORKDIR frontend" instruction) to use an absolute
directory for the frontend build directory that matches your repo layout.

🪄 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: Pro

Run ID: 12799d17-97a2-44eb-97f3-5c3732a321c4

📥 Commits

Reviewing files that changed from the base of the PR and between 2e67298 and 5dba68f.

📒 Files selected for processing (2)

Dockerfile
frontend/.yarnrc.yml

📜 Review details

🧰 Additional context used

📓 Path-based instructions (1)

**

⚙️ CodeRabbit configuration file

-Focus on major issues impacting performance, readability, maintainability and security. Avoid nitpicks and avoid verbosity.

Files:

Dockerfile

🪛 Hadolint (2.14.0)

Dockerfile

[error] 18-18: Use absolute WORKDIR

(DL3000)

🪛 Trivy (0.69.3)

Dockerfile

[error] 18-18: WORKDIR path not absolute

WORKDIR path 'frontend' should be absolute

Rule: DS-0009

Learn more

(IaC/Dockerfile)

🔇 Additional comments (2)

frontend/.yarnrc.yml (1)

13-16: Solid multi-arch configuration.

The supportedArchitectures block correctly declares the target platforms for hermetic builds. This ensures Yarn fetches native bindings for all four CPU architectures during dependency resolution, which is exactly what's needed for cross-platform container builds.

Dockerfile (1)

21-22: Clean simplification of the build flow.

Direct yarn invocation with --immutable is the right call for hermetic builds—ensures lockfile integrity and removes the cachito/corepack dance. Version-pinned yarn path keeps builds reproducible.

coderabbitai · 2026-03-31T11:38:15Z

- && cp -f $REMOTE_SOURCES_DIR/cachito-gomod-with-deps/app/frontend/{.npmrc,.yarnrc.yml,yarn.lock} frontend/
-
-# prevent download of cypress binary as part of module installs
+WORKDIR frontend


⚠️ Potential issue | 🟡 Minor

Use absolute WORKDIR for clarity and robustness.

Static analysis correctly flags this. While the relative path works (base image sets /opt/app-root/src), an absolute path makes the build self-documenting and immune to upstream base image changes.

🔧 Proposed fix

-WORKDIR frontend +WORKDIR /opt/app-root/src/frontend

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

WORKDIR frontend

WORKDIR /opt/app-root/src/frontend

🧰 Tools

🪛 Hadolint (2.14.0)

[error] 18-18: Use absolute WORKDIR

(DL3000)

🪛 Trivy (0.69.3)

[error] 18-18: WORKDIR path not absolute

WORKDIR path 'frontend' should be absolute

Rule: DS-0009

Learn more

(IaC/Dockerfile)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed. In `@Dockerfile` at line 18, The Dockerfile uses a relative WORKDIR ("WORKDIR frontend") which is brittle; replace that WORKDIR instruction with an absolute path instead so the build is explicit and not dependent on the base image's CWD—update the WORKDIR line in the Dockerfile (the "WORKDIR frontend" instruction) to use an absolute directory for the frontend build directory that matches your repo layout.

logonoff · 2026-03-31T14:40:19Z

/retitle NO-JIRA: enable multi-architecture yarn builds

logonoff · 2026-03-31T14:40:28Z

/label px-approved
/label docs-approved
/verified by CI

openshift-ci-robot · 2026-03-31T14:40:35Z

@lgarciaaco: This pull request explicitly references no jira issue.

Details

In response to this:

Summary

Enable multi-architecture yarn builds with hermetic build support

Changes

Convert Dockerfile to use hermetic build approach with cachi2 and add support for multiple architectures (x64, arm64, s390x, ppc64) in yarn configuration. This resolves hermetic build failures on non-x86_64 architectures by ensuring all required architecture-specific packages are included in dependency resolution.

Summary by CodeRabbit

Chores

Streamlined frontend build pipeline for improved maintainability

Extended platform architecture support for Linux deployments (x64, arm64, s390x, ppc64)

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-03-31T14:40:42Z

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

Details

In response to this:

/label px-approved
/label docs-approved
/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.

Convert Dockerfile to use hermetic build approach with cachi2 and add support for multiple architectures (x64, arm64, s390x, ppc64) in yarn configuration. This resolves hermetic build failures on non-x86_64 architectures by ensuring all required architecture-specific packages are included in dependency resolution. The change simplifies the build process by removing complex corepack setup and cachito integration in favor of the standard hermetic build pattern used across OpenShift components.

logonoff · 2026-04-01T12:03:33Z

/lgtm
/verified by CI

openshift-ci-robot · 2026-04-01T12:03:47Z

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

Details

In response to this:

/lgtm
/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.

jhadvig

/approve

logonoff · 2026-05-08T16:40:48Z

/cherry-pick release-4.22

openshift-cherrypick-robot · 2026-05-08T16:41:56Z

@logonoff: new pull request created: #16415

Details

In response to this:

/cherry-pick 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.

logonoff · 2026-05-08T16:42:04Z

/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19
/cherry-pick release-4.18
/cherry-pick release-4.17
/cherry-pick release-4.16
/cherry-pick release-4.15
/cherry-pick release-4.14
/cherry-pick release-4.13
/cherry-pick release-4.12

openshift-cherrypick-robot · 2026-05-08T16:42:47Z

@logonoff: #16228 failed to apply on top of branch "release-4.12":

Applying: build(frontend): enable multi-architecture yarn builds
Using index info to reconstruct a base tree...
M	Dockerfile
Falling back to patching base and 3-way merge...
Auto-merging Dockerfile
CONFLICT (content): Merge conflict in Dockerfile
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 build(frontend): enable multi-architecture yarn builds

Details

In response to this:

/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19
/cherry-pick release-4.18
/cherry-pick release-4.17
/cherry-pick release-4.16
/cherry-pick release-4.15
/cherry-pick release-4.14
/cherry-pick release-4.13
/cherry-pick release-4.12

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.

openshift-cherrypick-robot · 2026-05-08T16:43:28Z

@logonoff: #16228 failed to apply on top of branch "release-4.13":

Applying: build(frontend): enable multi-architecture yarn builds
Using index info to reconstruct a base tree...
M	Dockerfile
Falling back to patching base and 3-way merge...
Auto-merging Dockerfile
CONFLICT (content): Merge conflict in Dockerfile
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 build(frontend): enable multi-architecture yarn builds

Details

In response to this:

/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19
/cherry-pick release-4.18
/cherry-pick release-4.17
/cherry-pick release-4.16
/cherry-pick release-4.15
/cherry-pick release-4.14
/cherry-pick release-4.13
/cherry-pick release-4.12

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.

openshift-cherrypick-robot · 2026-05-08T16:43:59Z

@logonoff: new pull request created: #16416

Details

In response to this:

/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19

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.

openshift-cherrypick-robot · 2026-05-08T16:44:08Z

@logonoff: new pull request created: #16417

Details

In response to this:

/cherry-pick release-4.18
/cherry-pick release-4.17
/cherry-pick release-4.16

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.

openshift-cherrypick-robot · 2026-05-08T16:44:09Z

@logonoff: #16228 failed to apply on top of branch "release-4.14":

Applying: build(frontend): enable multi-architecture yarn builds
Using index info to reconstruct a base tree...
M	Dockerfile
Falling back to patching base and 3-way merge...
Auto-merging Dockerfile
CONFLICT (content): Merge conflict in Dockerfile
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 build(frontend): enable multi-architecture yarn builds

Details

In response to this:

/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19
/cherry-pick release-4.18
/cherry-pick release-4.17
/cherry-pick release-4.16
/cherry-pick release-4.15
/cherry-pick release-4.14
/cherry-pick release-4.13
/cherry-pick release-4.12

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.

openshift-cherrypick-robot · 2026-05-08T16:44:49Z

@logonoff: new pull request created: #16418

Details

In response to this:

/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19

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.

openshift-cherrypick-robot · 2026-05-08T16:44:50Z

@logonoff: #16228 failed to apply on top of branch "release-4.15":

Applying: build(frontend): enable multi-architecture yarn builds
Using index info to reconstruct a base tree...
M	Dockerfile
Falling back to patching base and 3-way merge...
Auto-merging Dockerfile
CONFLICT (content): Merge conflict in Dockerfile
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 build(frontend): enable multi-architecture yarn builds

Details

In response to this:

/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19
/cherry-pick release-4.18
/cherry-pick release-4.17
/cherry-pick release-4.16
/cherry-pick release-4.15
/cherry-pick release-4.14
/cherry-pick release-4.13
/cherry-pick release-4.12

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.

openshift-cherrypick-robot · 2026-05-08T16:44:52Z

@logonoff: new pull request created: #16419

Details

In response to this:

/cherry-pick release-4.18
/cherry-pick release-4.17
/cherry-pick release-4.16

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.

openshift-cherrypick-robot · 2026-05-08T16:45:32Z

@logonoff: new pull request created: #16420

Details

In response to this:

/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19

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.

openshift-cherrypick-robot · 2026-05-08T16:45:33Z

@logonoff: new pull request could not be created: failed to create pull request against openshift/console#release-4.16 from head openshift-cherrypick-robot:cherry-pick-16228-to-release-4.16: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-16228-to-release-4.16."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

Details

In response to this:

/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19
/cherry-pick release-4.18
/cherry-pick release-4.17
/cherry-pick release-4.16
/cherry-pick release-4.15
/cherry-pick release-4.14
/cherry-pick release-4.13
/cherry-pick release-4.12

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.

openshift-cherrypick-robot · 2026-05-08T16:45:36Z

@logonoff: new pull request created: #16421

Details

In response to this:

/cherry-pick release-4.18
/cherry-pick release-4.17
/cherry-pick release-4.16

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.

openshift-cherrypick-robot · 2026-05-08T16:46:17Z

@logonoff: new pull request could not be created: failed to create pull request against openshift/console#release-4.17 from head openshift-cherrypick-robot:cherry-pick-16228-to-release-4.17: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-16228-to-release-4.17."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

Details

In response to this:

/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19
/cherry-pick release-4.18
/cherry-pick release-4.17
/cherry-pick release-4.16
/cherry-pick release-4.15
/cherry-pick release-4.14
/cherry-pick release-4.13
/cherry-pick release-4.12

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.

openshift-cherrypick-robot · 2026-05-08T16:47:01Z

@logonoff: new pull request could not be created: failed to create pull request against openshift/console#release-4.18 from head openshift-cherrypick-robot:cherry-pick-16228-to-release-4.18: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-16228-to-release-4.18."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

Details

In response to this:

/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19
/cherry-pick release-4.18
/cherry-pick release-4.17
/cherry-pick release-4.16
/cherry-pick release-4.15
/cherry-pick release-4.14
/cherry-pick release-4.13
/cherry-pick release-4.12

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.

openshift-cherrypick-robot · 2026-05-08T16:47:44Z

@logonoff: new pull request could not be created: failed to create pull request against openshift/console#release-4.19 from head openshift-cherrypick-robot:cherry-pick-16228-to-release-4.19: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-16228-to-release-4.19."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

Details

In response to this:

/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19
/cherry-pick release-4.18
/cherry-pick release-4.17
/cherry-pick release-4.16
/cherry-pick release-4.15
/cherry-pick release-4.14
/cherry-pick release-4.13
/cherry-pick release-4.12

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.

openshift-cherrypick-robot · 2026-05-08T16:48:24Z

@logonoff: new pull request could not be created: failed to create pull request against openshift/console#release-4.20 from head openshift-cherrypick-robot:cherry-pick-16228-to-release-4.20: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-16228-to-release-4.20."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

Details

In response to this:

/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19
/cherry-pick release-4.18
/cherry-pick release-4.17
/cherry-pick release-4.16
/cherry-pick release-4.15
/cherry-pick release-4.14
/cherry-pick release-4.13
/cherry-pick release-4.12

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.

openshift-cherrypick-robot · 2026-05-08T16:49:04Z

@logonoff: new pull request could not be created: failed to create pull request against openshift/console#release-4.21 from head openshift-cherrypick-robot:cherry-pick-16228-to-release-4.21: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-16228-to-release-4.21."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

Details

In response to this:

/cherry-pick release-4.21
/cherry-pick release-4.20
/cherry-pick release-4.19
/cherry-pick release-4.18
/cherry-pick release-4.17
/cherry-pick release-4.16
/cherry-pick release-4.15
/cherry-pick release-4.14
/cherry-pick release-4.13
/cherry-pick release-4.12

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.

openshift-ci Bot requested review from jhadvig and rhamilto March 31, 2026 11:35

coderabbitai Bot reviewed Mar 31, 2026

View reviewed changes

openshift-ci Bot changed the title ~~build(frontend): enable multi-architecture yarn builds~~ NO-JIRA: enable multi-architecture yarn builds Mar 31, 2026

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

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 31, 2026

openshift-ci Bot added px-approved Signifies that Product Support has signed off on this PR docs-approved Signifies that Docs has signed off on this PR labels Mar 31, 2026

logonoff reviewed Mar 31, 2026

View reviewed changes

Comment thread frontend/.yarnrc.yml Outdated

lgarciaaco force-pushed the release-5.0 branch from 5dba68f to ca9b15e Compare April 1, 2026 07:35

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

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 1, 2026

openshift-ci Bot assigned logonoff Apr 1, 2026

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

jhadvig approved these changes Apr 8, 2026

View reviewed changes

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

jhadvig added plugin-api-approved Indicates a PR with plugin API changes has been approved by an API reviewer and removed approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Apr 8, 2026

logonoff mentioned this pull request Apr 8, 2026

console: update cachito config openshift-eng/ocp-build-data#9512

Closed

openshift-cherrypick-robot mentioned this pull request May 8, 2026

[release-4.22] NO-JIRA: enable multi-architecture yarn builds #16415

Merged

openshift-cherrypick-robot mentioned this pull request May 8, 2026

[release-4.19] NO-JIRA: enable multi-architecture yarn builds #16416

Merged

openshift-cherrypick-robot mentioned this pull request May 8, 2026

[release-4.16] NO-JIRA: enable multi-architecture yarn builds #16417

Merged

openshift-cherrypick-robot mentioned this pull request May 8, 2026

[release-4.20] NO-JIRA: enable multi-architecture yarn builds #16418

Merged

openshift-cherrypick-robot mentioned this pull request May 8, 2026

[release-4.17] NO-JIRA: enable multi-architecture yarn builds #16419

Merged

openshift-cherrypick-robot mentioned this pull request May 8, 2026

[release-4.21] NO-JIRA: enable multi-architecture yarn builds #16420

Merged

openshift-cherrypick-robot mentioned this pull request May 8, 2026

[release-4.18] NO-JIRA: enable multi-architecture yarn builds #16421

Merged

Conversation

lgarciaaco commented Mar 31, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Mar 31, 2026

Walkthrough

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

logonoff commented Mar 31, 2026

Uh oh!

logonoff commented Mar 31, 2026

Uh oh!

openshift-ci-robot commented Mar 31, 2026

Summary

Changes

Summary by CodeRabbit

Uh oh!

openshift-ci-robot commented Mar 31, 2026

Uh oh!

Uh oh!

logonoff commented Apr 1, 2026

Uh oh!

openshift-ci-robot commented Apr 1, 2026

Uh oh!

jhadvig left a comment

Choose a reason for hiding this comment

Uh oh!

logonoff commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

logonoff commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

openshift-cherrypick-robot commented May 8, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

lgarciaaco commented Mar 31, 2026 •

edited by coderabbitai Bot

Loading