NE-2823: Promote Multi HAProxy Versions feature to default by jcmoraisjr · Pull Request #2947 · openshift/api

jcmoraisjr · 2026-07-23T15:03:01Z

Promote the IngressControllerMultipleHAProxyVersions feature gate to the default featureset.

https://redhat.atlassian.net/browse/NE-2823

Promote the IngressControllerMultipleHAProxyVersions feature gate to the default featureset. https://redhat.atlassian.net/browse/NE-2823

openshift-merge-bot · 2026-07-23T15:03:03Z

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

openshift-ci-robot · 2026-07-23T15:03:05Z

@jcmoraisjr: This pull request references NE-2823 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:

Promote the IngressControllerMultipleHAProxyVersions feature gate to the default featureset.

https://redhat.atlassian.net/browse/NE-2823

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 · 2026-07-23T15:03:21Z

📝 Walkthrough

Walkthrough

IngressControllerMultipleHAProxyVersions now enables for default and OKD contexts in its feature-gate declaration. Its documentation entry was repositioned, and the 4.10 HyperShift and self-managed HA Default and OKD manifests now list the gate as enabled instead of disabled.

Suggested reviewers: sadasu, vr4manta

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
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.
Stable And Deterministic Test Names	✅ Passed	No Ginkgo spec titles were added or changed; the diff only updates feature-gate docs/manifests and generated CRDs.
Test Structure And Quality	✅ Passed	PR only changes feature-gate metadata/code and CRD manifests; no Ginkgo test code was added or modified.
Microshift Test Compatibility	✅ Passed	No Ginkgo e2e tests were added or modified; the PR only changes feature-gate config and generated CRD/manifests.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	No new Ginkgo/e2e tests were added; the commit only updates feature-gate docs/config and generated CRD manifests.
Topology-Aware Scheduling Compatibility	✅ Passed	PR only promotes the HAProxy-version feature gate and adds CRD fields; no node selectors, affinity, topology-spread, PDB, or topology assumptions changed.
Ote Binary Stdout Contract	✅ Passed	Only feature-gate config/registration changed; the affected Go helpers are pure builders and a search found no stdout/logging writes in process-level code.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Commit only updates feature-gate docs/manifests and registration; no new Ginkgo e2e tests or network-dependent test code were added.
No-Weak-Crypto	✅ Passed	No weak crypto was introduced; DES-CBC3-SHA was pre-existing in the CRD manifests, while the diff only promotes the feature gate.
Container-Privileges	✅ Passed	PASS: The diff only adds HAProxy version schema/feature-gate entries; no privileged, hostPID/hostIPC, runAsUser:0, or allowPrivilegeEscalation fields were added.
No-Sensitive-Data-In-Logs	✅ Passed	The diff only promotes a feature gate in Go/YAML/CRD manifests; it adds no logging code or sensitive-data output.
Title check	✅ Passed	The title clearly summarizes the main change: promoting Multi HAProxy Versions to the default featureset.
Description check	✅ Passed	The description is directly related to the change and matches the feature-gate promotion in the PR.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

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.}

openshift-ci · 2026-07-23T15:03:30Z

Hello @jcmoraisjr! 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.

qodo-for-rh-openshift · 2026-07-23T15:04:09Z

PR Summary by Qodo

Promote Multi-HAProxy versions feature gate to Default/OKD

✨ Enhancement ⚙️ Configuration changes 📝 Documentation 🕐 20-40 Minutes

AI Description

• Enable IngressControllerMultipleHAProxyVersions in the default and OKD feature sets.
• Publish IngressController API fields for pinning/reporting HAProxy version.
• Update feature gate payload manifests and feature table documentation.

Diagram

graph TD
  A["features/features.go"] --> B["payload featuregates"] --> C[Ingress operator] --> D[(IngressController CRD)] --> E[IngressController instances] --> F[HAProxy deployment]
  G["features.md"]

High-Level Assessment

Promoting the feature gate to the Default/OKD feature sets is the appropriate mechanism for making the capability generally available. The PR keeps the change constrained to feature registration, payload feature lists, and generated API surface documentation/manifests, which is the standard rollout pattern for OpenShift feature gates.

Files changed (8) +94 / -14

Enhancement (2) +80 / -0

0000_50_ingress_00_ingresscontrollers-Default.crd.yamlExpose haproxyVersion (spec) and effectiveHAProxyVersion (status) in Default CRD +40/-0

Expose haproxyVersion (spec) and effectiveHAProxyVersion (status) in Default CRD
• Adds a spec.haproxyVersion field (enum "2.8"/"3.2") to allow pinning/selecting HAProxy versions, and a status.effectiveHAProxyVersion field to report the resolved version currently in use.
operator/v1/zz_generated.crd-manifests/0000_50_ingress_00_ingresscontrollers-Default.crd.yaml

0000_50_ingress_00_ingresscontrollers-OKD.crd.yamlExpose haproxyVersion (spec) and effectiveHAProxyVersion (status) in OKD CRD +40/-0

Expose haproxyVersion (spec) and effectiveHAProxyVersion (status) in OKD CRD
• Mirrors the Default CRD changes for OKD: adds spec.haproxyVersion for version selection/pinning and status.effectiveHAProxyVersion for reporting the resolved HAProxy version.
operator/v1/zz_generated.crd-manifests/0000_50_ingress_00_ingresscontrollers-OKD.crd.yaml

Documentation (1) +1 / -1

features.mdMove Multi-HAProxy versions gate into the default-enabled features table section +1/-1

Move Multi-HAProxy versions gate into the default-enabled features table section
• Repositions the IngressControllerMultipleHAProxyVersions entry in the feature gate matrix to reflect promotion to default enablement across profiles/releases shown in the table.
features.md

Other (5) +13 / -13

features.goEnable IngressControllerMultipleHAProxyVersions in Default and OKD feature sets +1/-1

Enable IngressControllerMultipleHAProxyVersions in Default and OKD feature sets
• Updates the feature gate registration so IngressControllerMultipleHAProxyVersions is enabled in inDefault() and inOKD(), in addition to the existing dev/tech preview no-upgrade sets.
features/features.go

featureGate-4-10-Hypershift-Default.yamlAdd Multi-HAProxy versions to Hypershift Default enabled features +3/-3

Add Multi-HAProxy versions to Hypershift Default enabled features
• Moves IngressControllerMultipleHAProxyVersions from the earlier list to the default-enabled feature list so it is enabled by default for this profile.
payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yaml

featureGate-4-10-Hypershift-OKD.yamlAdd Multi-HAProxy versions to Hypershift OKD enabled features +3/-3

Add Multi-HAProxy versions to Hypershift OKD enabled features
• Moves IngressControllerMultipleHAProxyVersions into the default-enabled feature list for the Hypershift OKD profile.
payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yaml

featureGate-4-10-SelfManagedHA-Default.yamlAdd Multi-HAProxy versions to SelfManagedHA Default enabled features +3/-3

Add Multi-HAProxy versions to SelfManagedHA Default enabled features
• Moves IngressControllerMultipleHAProxyVersions into the default-enabled feature list for SelfManagedHA Default.
payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-Default.yaml

featureGate-4-10-SelfManagedHA-OKD.yamlAdd Multi-HAProxy versions to SelfManagedHA OKD enabled features +3/-3

Add Multi-HAProxy versions to SelfManagedHA OKD enabled features
• Moves IngressControllerMultipleHAProxyVersions into the default-enabled feature list for SelfManagedHA OKD.
payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-OKD.yaml

openshift-ci · 2026-07-23T15:06:06Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign joelspeed for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

OWNERS

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

qodo-for-rh-openshift · 2026-07-23T15:10:24Z

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

⚠️ Tickets: not configured — ticket URL found in PR but could not be fetched — check ticket provider credentials

✅ Compliance rules (platform): 29 rules

✅ Skills: api-review

1. 5.0-only value exposed 🐞 Bug ≡ Correctness

Description

IngressControllerMultipleHAProxyVersions is now enabled for the Default and OKD feature sets without
any OpenShift major-version constraint, which makes spec.haproxyVersion accept "3.2" even on
payloads that target major version 4. This contradicts the API documentation that describes HAProxy
3.2 as introduced in OpenShift 5.0 and can let OpenShift 4.x clusters pass API validation with a
value that may not be supported by that release’s ingress payload/operator logic.

Code

features/features.go[682]

+								enable(inDefault(), inOKD(), inDevPreviewNoUpgrade(), inTechPreviewNoUpgrade()).

Relevance

●●● Strong
Likely treated as backward-compat/correctness bug: avoid exposing 5.0-only API values on 4.x payload
validation.
PR-#2906
PR-#2784

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The PR change enables the gate in Default/OKD; the generated payload FeatureGate manifests apply to
major version 4 as well; and the API type/docs + enum explicitly frame 3.2 as an OpenShift 5.0
capability while still allowing it via validation.
features/features.go[677-683]
payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yaml[2-9]
operator/v1/types_ingresscontroller.go[389-413]
operator/v1/types_ingresscontroller.go[2373-2386]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The feature gate `IngressControllerMultipleHAProxyVersions` is now enabled in `Default` and `OKD` for all generated OpenShift major versions, but the API type/doc explicitly describes HAProxy `3.2` as an OpenShift 5.0 introduction. This means OpenShift major version 4 payloads will advertise and validate a value (`"3.2"`) that is documented as 5.0-only.

### Issue Context
- The feature-gate payloads are annotated for major versions `4,5,6,7,8,9,10`.
- The `HAProxyVersion` type is enum-constrained to `"2.8";"3.2"`.
- The `haproxyVersion` field description states HAProxy 3.2 is the OpenShift 5.0 default.

### Fix Focus Areas
- features/features.go[677-683]

### How to fix
Update the feature gate registration to only enable this gate in `Default`/`OKD` for OpenShift major version >= 5 (e.g., by adding `inVersion(5, greaterThanOrEqual)` to the enable options for `inDefault()` and `inOKD()`), or otherwise make the exposed/validated values release-aware so major version 4 payloads do not validate/advertise `"3.2"` as a supported setting.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}

Previous review results

Review updated until commit bb7402c ⚖️ Balanced

Results up to commit bb7402c ⚖️ Balanced

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. 5.0-only value exposed 🐞 Bug ≡ Correctness

Description

IngressControllerMultipleHAProxyVersions is now enabled for the Default and OKD feature sets without
any OpenShift major-version constraint, which makes spec.haproxyVersion accept "3.2" even on
payloads that target major version 4. This contradicts the API documentation that describes HAProxy
3.2 as introduced in OpenShift 5.0 and can let OpenShift 4.x clusters pass API validation with a
value that may not be supported by that release’s ingress payload/operator logic.

Code

features/features.go[682]

+								enable(inDefault(), inOKD(), inDevPreviewNoUpgrade(), inTechPreviewNoUpgrade()).

Relevance

●●● Strong
Likely treated as backward-compat/correctness bug: avoid exposing 5.0-only API values on 4.x payload
validation.
PR-#2906
PR-#2784

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The PR change enables the gate in Default/OKD; the generated payload FeatureGate manifests apply to
major version 4 as well; and the API type/docs + enum explicitly frame 3.2 as an OpenShift 5.0
capability while still allowing it via validation.
features/features.go[677-683]
payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yaml[2-9]
operator/v1/types_ingresscontroller.go[389-413]
operator/v1/types_ingresscontroller.go[2373-2386]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The feature gate `IngressControllerMultipleHAProxyVersions` is now enabled in `Default` and `OKD` for all generated OpenShift major versions, but the API type/doc explicitly describes HAProxy `3.2` as an OpenShift 5.0 introduction. This means OpenShift major version 4 payloads will advertise and validate a value (`"3.2"`) that is documented as 5.0-only.

### Issue Context
- The feature-gate payloads are annotated for major versions `4,5,6,7,8,9,10`.
- The `HAProxyVersion` type is enum-constrained to `"2.8";"3.2"`.
- The `haproxyVersion` field description states HAProxy 3.2 is the OpenShift 5.0 default.

### Fix Focus Areas
- features/features.go[677-683]

### How to fix
Update the feature gate registration to only enable this gate in `Default`/`OKD` for OpenShift major version >= 5 (e.g., by adding `inVersion(5, greaterThanOrEqual)` to the enable options for `inDefault()` and `inOKD()`), or otherwise make the exposed/validated values release-aware so major version 4 payloads do not validate/advertise `"3.2"` as a supported setting.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

qodo-for-rh-openshift · 2026-07-23T15:10:25Z

 								productScope(ocpSpecific).
 								enhancementPR("https://github.com/openshift/enhancements/pull/1965").
-								enable(inDevPreviewNoUpgrade(), inTechPreviewNoUpgrade()).
+								enable(inDefault(), inOKD(), inDevPreviewNoUpgrade(), inTechPreviewNoUpgrade()).


1. 5.0-only value exposed 🐞 Bug ≡ Correctness

IngressControllerMultipleHAProxyVersions is now enabled for the Default and OKD feature sets without any OpenShift major-version constraint, which makes spec.haproxyVersion accept "3.2" even on payloads that target major version 4. This contradicts the API documentation that describes HAProxy 3.2 as introduced in OpenShift 5.0 and can let OpenShift 4.x clusters pass API validation with a value that may not be supported by that release’s ingress payload/operator logic.

Agent Prompt

### Issue description The feature gate `IngressControllerMultipleHAProxyVersions` is now enabled in `Default` and `OKD` for all generated OpenShift major versions, but the API type/doc explicitly describes HAProxy `3.2` as an OpenShift 5.0 introduction. This means OpenShift major version 4 payloads will advertise and validate a value (`"3.2"`) that is documented as 5.0-only. ### Issue Context - The feature-gate payloads are annotated for major versions `4,5,6,7,8,9,10`. - The `HAProxyVersion` type is enum-constrained to `"2.8";"3.2"`. - The `haproxyVersion` field description states HAProxy 3.2 is the OpenShift 5.0 default. ### Fix Focus Areas - features/features.go[677-683] ### How to fix Update the feature gate registration to only enable this gate in `Default`/`OKD` for OpenShift major version >= 5 (e.g., by adding `inVersion(5, greaterThanOrEqual)` to the enable options for `inDefault()` and `inOKD()`), or otherwise make the exposed/validated values release-aware so major version 4 payloads do not validate/advertise `"3.2"` as a supported setting.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

gcs278 · 2026-07-23T23:36:44Z

/test verify-feature-promotion

qodo-for-rh-openshift · 2026-07-23T23:37:01Z

PR-Agent: could not find a component named verify-feature-promotion in a supported language in this PR.

gcs278 · 2026-07-24T15:43:55Z

Qodo why do you think I'm talking to you?? lol

/test verify-feature-promotion

qodo-for-rh-openshift · 2026-07-24T15:44:25Z

Qodo why do you think I'm talking to you?? lol

/test verify-feature-promotion

Because your comment explicitly started with “Qodo,” so I treated it as addressing me—fair point if that was rhetorical. I can’t run /test verify-feature-promotion from this chat.

gcs278 · 2026-07-25T22:09:11Z

/test verify-feature-promotion

qodo-for-rh-openshift · 2026-07-25T22:09:35Z

PR-Agent: could not find a component named verify-feature-promotion in a supported language in this PR.

gcs278 · 2026-07-26T19:44:16Z

/test verify-feature-promotion

qodo-for-rh-openshift · 2026-07-26T19:45:01Z

PR-Agent: could not find a component named verify-feature-promotion in a supported language in this PR.

gcs278 · 2026-07-27T12:05:05Z

/test verify-feature-promotion

qodo-for-rh-openshift · 2026-07-27T12:06:01Z

PR-Agent: could not find a component named verify-feature-promotion in a supported language in this PR.

gcs278 · 2026-07-27T19:39:52Z

/test verify-feature-promotion

qodo-for-rh-openshift · 2026-07-27T19:40:22Z

PR-Agent: could not find a component named verify-feature-promotion in a supported language in this PR.

gcs278 · 2026-07-28T00:43:11Z

/test verify-feature-promotion

qodo-for-rh-openshift · 2026-07-28T00:43:41Z

PR-Agent: could not find a component named verify-feature-promotion in a supported language in this PR.

gcs278 · 2026-07-28T13:00:48Z

/test verify-feature-promotion

qodo-for-rh-openshift · 2026-07-28T13:01:32Z

PR-Agent: could not find a component named verify-feature-promotion in a supported language in this PR.

gcs278 · 2026-07-29T00:18:13Z

/test verify-feature-promotion

qodo-for-rh-openshift · 2026-07-29T00:18:55Z

PR-Agent: could not find a component named verify-feature-promotion in a supported language in this PR.

gcs278 · 2026-07-29T17:10:07Z

/test verify-feature-promotion

qodo-for-rh-openshift · 2026-07-29T17:11:26Z

PR-Agent: could not find a component named verify-feature-promotion in a supported language in this PR.

openshift-ci · 2026-07-29T17:15:41Z

@jcmoraisjr: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/verify-hypershift-integration	`bb7402c`	link	true	`/test verify-hypershift-integration`
ci/prow/verify-feature-promotion	`bb7402c`	link	true	`/test verify-feature-promotion`

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.

gcs278 · 2026-07-29T20:05:16Z

/test verify-feature-promotion

gcs278 · 2026-07-29T20:05:51Z

/test verify
/test verify-hypershift-integration

qodo-for-rh-openshift · 2026-07-29T20:06:03Z

PR-Agent: could not find a component named verify-feature-promotion in a supported language in this PR.

qodo-for-rh-openshift · 2026-07-29T20:07:15Z

PR-Agent: could not find a component named verify in a supported language in this PR.

qodo-for-rh-openshift · 2026-07-29T20:33:35Z

Code review by qodo was updated up to the latest commit bb7402c

jcmoraisjr · 2026-07-29T20:35:29Z

/pipeline required

openshift-merge-bot · 2026-07-29T20:35:32Z

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

gcs278 · 2026-07-29T22:52:53Z

unrelated
/retest

Promote Multi HAProxy Versions feature to default

bb7402c

Promote the IngressControllerMultipleHAProxyVersions feature gate to the default featureset. https://redhat.atlassian.net/browse/NE-2823

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

openshift-ci Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jul 23, 2026

jcmoraisjr changed the title ~~NE-2823: Promote Multi HAProxy Versions feature to default~~ Draft: NE-2823: Promote Multi HAProxy Versions feature to default Jul 23, 2026

openshift-ci Bot requested review from JoelSpeed and everettraven July 23, 2026 15:06

qodo-for-rh-openshift Bot reviewed Jul 23, 2026

View reviewed changes

jcmoraisjr marked this pull request as draft July 23, 2026 15:22

openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 23, 2026

gcs278 mentioned this pull request Jul 23, 2026

NE-2789: Add a guard to skip IngressControllerMultipleHAProxyVersions tests if IngressController CRD lacks haproxyVersion field openshift/origin#31424

Merged

jcmoraisjr marked this pull request as ready for review July 29, 2026 20:27

openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 29, 2026

jcmoraisjr changed the title ~~Draft: NE-2823: Promote Multi HAProxy Versions feature to default~~ NE-2823: Promote Multi HAProxy Versions feature to default Jul 29, 2026

Uh oh!

Conversation

jcmoraisjr commented Jul 23, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 23, 2026

Uh oh!

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

Uh oh!

Uh oh!

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

Uh oh!

Walkthrough

Uh oh!

openshift-ci Bot commented Jul 23, 2026

Uh oh!

qodo-for-rh-openshift Bot commented Jul 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Summary by Qodo

Uh oh!

openshift-ci Bot commented Jul 23, 2026

Uh oh!

qodo-for-rh-openshift Bot commented Jul 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review by Qodo

Previous review results

Uh oh!

qodo-for-rh-openshift Bot Jul 23, 2026

Choose a reason for hiding this comment

Uh oh!

gcs278 commented Jul 23, 2026

Uh oh!

qodo-for-rh-openshift Bot commented Jul 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gcs278 commented Jul 24, 2026

Uh oh!

qodo-for-rh-openshift Bot commented Jul 24, 2026

Uh oh!

gcs278 commented Jul 25, 2026

Uh oh!

qodo-for-rh-openshift Bot commented Jul 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gcs278 commented Jul 26, 2026

Uh oh!

qodo-for-rh-openshift Bot commented Jul 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gcs278 commented Jul 27, 2026

Uh oh!

qodo-for-rh-openshift Bot commented Jul 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gcs278 commented Jul 27, 2026

Uh oh!

qodo-for-rh-openshift Bot commented Jul 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gcs278 commented Jul 28, 2026

Uh oh!

qodo-for-rh-openshift Bot commented Jul 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gcs278 commented Jul 28, 2026

Uh oh!

qodo-for-rh-openshift Bot commented Jul 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gcs278 commented Jul 29, 2026

Uh oh!

qodo-for-rh-openshift Bot commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gcs278 commented Jul 29, 2026

Uh oh!

qodo-for-rh-openshift Bot commented Jul 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci Bot commented Jul 29, 2026

Uh oh!

openshift-ci-robot commented Jul 23, 2026 •

edited by openshift-ci Bot

Loading

coderabbitai Bot commented Jul 23, 2026 •

edited

Loading

qodo-for-rh-openshift Bot commented Jul 23, 2026 •

edited

Loading

qodo-for-rh-openshift Bot commented Jul 23, 2026 •

edited

Loading

qodo-for-rh-openshift Bot commented Jul 23, 2026 •

edited

Loading

qodo-for-rh-openshift Bot commented Jul 25, 2026 •

edited

Loading

qodo-for-rh-openshift Bot commented Jul 26, 2026 •

edited

Loading

qodo-for-rh-openshift Bot commented Jul 27, 2026 •

edited

Loading

qodo-for-rh-openshift Bot commented Jul 27, 2026 •

edited

Loading

qodo-for-rh-openshift Bot commented Jul 28, 2026 •

edited

Loading

qodo-for-rh-openshift Bot commented Jul 28, 2026 •

edited

Loading

qodo-for-rh-openshift Bot commented Jul 29, 2026 •

edited

Loading

qodo-for-rh-openshift Bot commented Jul 29, 2026 •

edited

Loading

qodo-for-rh-openshift Bot commented Jul 29, 2026 •

edited

Loading

qodo-for-rh-openshift Bot commented Jul 29, 2026 •

edited

Loading