NE-2520: Promote GatewayAPIWithoutOLM to GA by gcs278 · Pull Request #2772 · openshift/api

gcs278 · 2026-03-18T20:05:16Z

This PR promotes the GatewayAPIWithoutOLM feature gate from TechPreviewNoUpgrade to Default (GA).

Background

The GatewayAPIWithoutOLM feature replaces the OLM-based Istio installation method with direct Helm chart installation via the Sail library, enabling Gateway API support on clusters without OLM/Marketplace capabilities and avoiding conflicts with existing OSSM subscriptions.

Related Work

Enhancement: NE-2470: Gateway API without OLM
Implementation: cluster-ingress-operator#1354
Jira Epic: NE-2520

Testing

Sippy: GatewayAPIWithoutOLM Results
Existing E2E tests adapted in cluster-ingress-operator gateway_api_test.go for more coverage
Upgrade test: origin#30897 validates OLM to NO-OLM migration; tested manually (TechPreview clusters cannot be upgraded in CI), will merge soon and shouldn't block promotion

openshift-ci-robot · 2026-03-18T20:05:20Z

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-03-18T20:05:22Z

@gcs278: This pull request references NE-2520 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 "4.22.0" version, but no target version was set.

Details

In response to this:

WIP DO NOT MERGE: Using this for testing

This change promotes the GatewayAPIWithoutOLM feature gate from TechPreviewNoUpgrade to Default Feature Set (GA).

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-03-18T20:05:23Z

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

openshift-ci · 2026-03-18T20:05:24Z

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

coderabbitai · 2026-03-18T20:05:26Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro

Run ID: 8e7ffeb7-bd69-46ed-8274-abcaf9bdf489

📥 Commits

Reviewing files that changed from the base of the PR and between 64340c4 and 71580b7.

📒 Files selected for processing (6)

features.md
features/features.go
payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yaml
payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yaml
payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-Default.yaml
payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-OKD.yaml

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

features.md

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

payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-Default.yaml
features/features.go
payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yaml

📝 Walkthrough

Walkthrough

The GatewayAPIWithoutOLM feature gate is enabled in additional contexts. The feature gate registration in features/features.go now includes inDefault() and inOKD() alongside inDevPreviewNoUpgrade() and inTechPreviewNoUpgrade(). Corresponding payload feature-gate YAMLs for Hypershift and SelfManagedHA (Default and OKD variants) move GatewayAPIWithoutOLM from status.featureGates[].disabled to status.featureGates[].enabled. features.md reorders the GatewayAPIWithoutOLM row in the feature table.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Warning

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

🔧 golangci-lint (2.11.4)

Error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented
The command is terminated due to an error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented

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

openshift-ci · 2026-03-18T20:12:28Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c6220410-2306-11f1-9c3a-90af7c7cc380-0

openshift-ci · 2026-03-18T20:15:19Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/23e6af60-2307-11f1-992d-12ede9d2e079-0

openshift-ci · 2026-03-18T20:15:32Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/26a088fc-2307-11f1-9da4-6bca82f01e76-0

openshift-ci · 2026-03-18T20:34:41Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e01ef8c0-2309-11f1-813c-239011e41911-0

openshift-ci · 2026-03-19T02:54:58Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0198a9d0-233f-11f1-9a7d-ebebc862b301-0

openshift-ci · 2026-03-19T12:42:32Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/07dadcd0-2391-11f1-8c59-fe2512e5aad1-0

openshift-ci-robot · 2026-03-19T14:11:04Z

@gcs278: This pull request references NE-2520 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 "4.22.0" version, but no target version was set.

Details

In response to this:

WIP DO NOT MERGE (yet): Using this for testing

This change promotes the GatewayAPIWithoutOLM feature gate from TechPreviewNoUpgrade to Default Feature Set (GA).

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-03-19T19:01:36Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0ab81910-23c6-11f1-8635-bf728c1f5aad-0

openshift-ci · 2026-03-20T02:40:27Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/1e4a3720-2406-11f1-93e5-9f16732fd0e5-0

openshift-ci · 2026-03-20T19:29:09Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0ddd5ec0-2493-11f1-8cf8-effe9a495bea-0

openshift-ci · 2026-03-21T01:51:05Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/69a77f80-24c8-11f1-9403-ad1a7c99fb97-0

openshift-ci · 2026-03-21T01:51:59Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8a761690-24c8-11f1-9c74-da2cb51d6692-0

openshift-ci-robot · 2026-03-23T19:44:17Z

@gcs278: This pull request references NE-2561 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 "4.22.0" version, but no target version was set.

Details

In response to this:

WIP DO NOT MERGE (yet): Using this for testing

This change promotes the GatewayAPIWithoutOLM feature gate from TechPreviewNoUpgrade to Default Feature Set (GA).

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-23T19:46:48Z

@gcs278: This pull request references NE-2520 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 "4.22.0" version, but no target version was set.

Details

In response to this:

WIP DO NOT MERGE (yet): Using this for testing

This change promotes the GatewayAPIWithoutOLM feature gate from TechPreviewNoUpgrade to Default Feature Set (GA).

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-03-23T23:31:38Z

@gcs278: This PR was included in a payload test run from openshift/origin#30897
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6d5568f0-2710-11f1-9d03-561b26d4f2f7-0

everettraven · 2026-04-06T18:11:09Z

We don't support dual stack/IPv6, see openshift/origin#30942

Looks like the linked PR only removes support for dual stack, not IPv6 - just to make sure, we are certain we do not support ipv6 networking for this feature?

everettraven · 2026-04-06T18:15:03Z

whether we can accept the risk of promotion with limit vsphere/metal testing.

My general stance is that if we have (or should have) signal for a platform, we shouldn't be promoting until the criteria are met. If the promotion is urgent, the OpenShift architects and the BU are the ones that need to make the decision on whether or not a promotion goes through without sufficient testing via an SBAR.

In this case, I'd say lets just collect the runs. If you need extra runs you can use the gangway cli (https://github.com/openshift-eng/gangway-cli) to trigger more job runs.

gcs278 · 2026-04-06T19:26:34Z

Looks like the linked PR only removes support for dual stack, not IPv6 - just to make sure, we are certain we do not support ipv6 networking for this feature?

Yes, I'm certain. Though we do claim support for Metal/VSphere (NE-2010), we do not claim support for IPv6 and DualStack for the entire Gateway API feature. We don't run tests on it today, and when I tried to enable it for IPv6, Gateway API doesn't work. And my feature (GatewayAPIWithoutOLM) is a "child feature" that is dependent on Gateway API functioning.

In this case, I'd say lets just collect the runs. If you need extra runs you can use the gangway cli (https://github.com/openshift-eng/gangway-cli) to trigger more job runs.

Agreed, I added them last week in openshift/origin#30946 (I forgot to link here). We are getting signal now, but it looks like we are at 87% for Vsphere for this specific test (2/16 flaked):

][apigroup:gateway.networking.k8s.io] [OCPFeatureGate:GatewayAPIWithoutOLM] Ensure GatewayClass contains sail finalizer after creation [Suite:openshift/conformance/parallel]" only passed 87%, need at least 95% for "GatewayAPIWithoutOLM" on {vsphere amd64 ha    false}

The 2 flakes are due to the test hardness code for markTestDone (not the actual test). It's a classic "object has been modified" because the CIO now writes conditions to the GatewayClass, causing a conflict with the test harness code when it tries to write an annotation as a test-completion marker:

{  fail [github.com/openshift/origin/test/extended/router/gatewayapicontroller.go:1132]: Unexpected error:
    <*errors.StatusError | 0xc0096d74a0>: 
    Operation cannot be fulfilled on gatewayclasses.gateway.networking.k8s.io "openshift-default": the object has been modified; please apply your changes to the latest version and try again
    {
        ErrStatus: 
            code: 409
            details:
              group: gateway.networking.k8s.io
              kind: gatewayclasses
              name: openshift-default
            message: 'Operation cannot be fulfilled on gatewayclasses.gateway.networking.k8s.io
              "openshift-default": the object has been modified; please apply your changes to
              the latest version and try again'
            metadata: {}
            reason: Conflict
            status: Failure,
    }
occurred}

I have a fix up here for it openshift/origin#30964.

@JoelSpeed @everettraven would you consider allowing us to promote? I did the math, and we'd need 24 more tests to succeed in a row to get back to 95%. I don't think we have quite that runway at the moment. I could gangway the Vsphere tests, but it'd seem a bit hard on our VSphere resources (i'd need to run 6-7 times a day to get in by branch cut). I'm confident the VSphere feature functionality is working as expected.

To summarize the verify-feature-promotion failures:

IPv6 and DualStack are not supported for Gateway API, and GatewayAPIWithoutOLM depends on Gateway API functioning.
A new VSphere test is flaking at 87% (2/16) due to a test harness conflict, not a product bug. Fix is up: OCPBUGS-81751: Fix GatewayClass update conflict in markTestDone origin#30964.

Please let me know if you'd need anything from me.

JoelSpeed · 2026-04-07T11:00:22Z

/pipeline required

openshift-ci-robot · 2026-04-07T11:00:26Z

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

JoelSpeed · 2026-04-07T13:21:18Z

/test verify-feature-promotion

qodo-code-review · 2026-04-07T13:21:25Z

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

everettraven · 2026-04-07T13:48:35Z

Yes, I'm certain. Though we do claim support for Metal/VSphere (NE-2010), we do not claim support for IPv6 and DualStack for the entire Gateway API feature. We don't run tests on it today, and when I tried to enable it for IPv6, Gateway API doesn't work. And my feature (GatewayAPIWithoutOLM) is a "child feature" that is dependent on Gateway API functioning.

Thanks for the additional context.

would you consider allowing us to promote? I did the math, and we'd need 24 more tests to succeed in a row to get back to 95%. I don't think we have quite that runway at the moment. I could gangway the Vsphere tests, but it'd seem a bit hard on our VSphere resources (i'd need to run 6-7 times a day to get in by branch cut). I'm confident the VSphere feature functionality is working as expected.

My stance would be:

Let's get the flake fix in and gather enough more recent runs to build confidence that the flake no longer happens
Get the 95% pass rate OR have good signal towards 95% pass rate AND get an ACK from TRT and/or OCP Architects that they are OK with this going in with a lower pass rate for this platform. Keep in mind that anything with less than a 95% pass rate is considered a regression. Regressions cause issues when trying to get release candidates and the purpose of the "pencils down" is to start focusing on stability in preparation for getting release candidates out. The 95% passing rate rule is meant to ensure we aren't introducing instability here and without an explicit ACK from the ones impacted by instability that they are OK with this, I won't circumvent this requirement.

gcs278 · 2026-04-07T16:17:55Z

@everettraven Thanks - I understand the caution here given the timeline. Getting to 95% likely isn't going to work given our desired timeline of making branch cut (and we'd like to merge in the next day or so). So we will need to get folks to sign off.

To help illustrate my confidence:

The flake fix has merged OCPBUGS-81751: Fix GatewayClass update conflict in markTestDone origin#30964
In the last 24 hours we've gone from 87% to 90% on the latest verify-feature-promotion run for the flakey test (Ensure GatewayClass contains sail finalizer after creation)
The aggregate periodic job results for the flake fix OCPBUGS-81751: Fix GatewayClass update conflict in markTestDone origin#30964 showed that of the 4/10 vsphere clusters that installed successfully, none had the flake, and none had any GWAPI-related issues.
It's worth repeating the context: the flake happened on a defer cleanup function, so the core content of the test itself actually passed, but flake happened at the end.

CC: @JoelSpeed

JoelSpeed · 2026-04-07T16:50:52Z

Given the above, and that the only failures visible in sippy are from test cleanup which we are now confident is fixed

/override ci/prow/verify-feature-promotion

/lgtm
/verified by verify-feature-promotion

/retest

openshift-ci-robot · 2026-04-07T16:51:05Z

@JoelSpeed: This PR has been marked as verified by verify-feature-promotion.

Details

In response to this:

Given the above, and that the only failures visible in sippy are from test cleanup which we are now confident is fixed

/override ci/prow/verify-feature-promotion

/lgtm
/verified by verify-feature-promotion

/retest

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-04-07T16:51:10Z

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify-feature-promotion

Details

In response to this:

Given the above, and that the only failures visible in sippy are from test cleanup which we are now confident is fixed

/override ci/prow/verify-feature-promotion

/lgtm
/verified by verify-feature-promotion

/retest

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-robot · 2026-04-07T16:51:28Z

Tests from second stage were triggered manually. Pipeline can be controlled only manually, until HEAD changes. Use command to trigger second stage.

openshift-ci · 2026-04-07T16:51:28Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

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

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

openshift-merge-bot · 2026-04-07T17:49:23Z

/retest-required

Remaining retests: 0 against base HEAD f50e695 and 2 for PR HEAD 71580b7 in total

gcs278 · 2026-04-07T20:24:27Z

@JoelSpeed I think you'll need to re-apply the override.

openshift-merge-bot · 2026-04-07T21:17:20Z

/retest-required

Remaining retests: 0 against base HEAD d87d63a and 1 for PR HEAD 71580b7 in total

JoelSpeed · 2026-04-08T08:47:57Z

/override ci/prow/verify-feature-promotion
/override ci/prow/e2e-aws-ovn-hypershift-conformance

HyperShift conformance has a known image configuration issue

openshift-ci · 2026-04-08T08:48:05Z

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-aws-ovn-hypershift-conformance, ci/prow/verify-feature-promotion

Details

In response to this:

/override ci/prow/verify-feature-promotion
/override ci/prow/e2e-aws-ovn-hypershift-conformance

HyperShift conformance has a known image configuration issue

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.

JoelSpeed · 2026-04-08T08:49:29Z

/override ci/prow/e2e-azure

Failures appear to me to be unrelated

openshift-ci · 2026-04-08T08:49:36Z

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-azure

Details

In response to this:

/override ci/prow/e2e-azure

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-merge-bot · 2026-04-08T09:53:02Z

/retest-required

Remaining retests: 0 against base HEAD 8b086e6 and 0 for PR HEAD 71580b7 in total

JoelSpeed · 2026-04-08T10:35:34Z

/override ci/prow/verify-feature-promotion

openshift-ci · 2026-04-08T10:35:45Z

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify-feature-promotion

Details

In response to this:

/override ci/prow/verify-feature-promotion

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 · 2026-04-08T10:35:50Z

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

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

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 Mar 18, 2026

openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 18, 2026

gcs278 mentioned this pull request Mar 18, 2026

NE-2561: Add Gateway API OLM to NO-OLM migration upgrade test openshift/origin#30897

Open

gcs278 mentioned this pull request Mar 19, 2026

OCPBUGS-79667: Use feature-gate annotation for Sail Library RBAC openshift/cluster-ingress-operator#1393

Merged

gcs278 changed the title ~~[WIP] NE-2520: Promote GatewayAPIWithoutOLM to GA~~ [WIP] NE-2561: Promote GatewayAPIWithoutOLM to GA Mar 23, 2026

gcs278 changed the title ~~[WIP] NE-2561: Promote GatewayAPIWithoutOLM to GA~~ [WIP] NE-2520: Promote GatewayAPIWithoutOLM to GA Mar 23, 2026

openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 26, 2026

gcs278 force-pushed the GatewayAPIWithoutOLM-promote-GA branch from 70d9187 to 64340c4 Compare March 27, 2026 00:38

openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 27, 2026

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

openshift-ci bot assigned JoelSpeed Apr 7, 2026

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

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

openshift-merge-bot bot merged commit 9ed1def into openshift:master Apr 8, 2026
28 checks passed

Conversation

gcs278 commented Mar 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Background

Related Work

Testing

Uh oh!

openshift-ci-robot commented Mar 18, 2026

Uh oh!

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

Uh oh!

Uh oh!

openshift-ci bot commented Mar 18, 2026

Uh oh!

openshift-ci bot commented Mar 18, 2026

Uh oh!

coderabbitai bot commented Mar 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Uh oh!

openshift-ci bot commented Mar 18, 2026

Uh oh!

openshift-ci bot commented Mar 18, 2026

Uh oh!

openshift-ci bot commented Mar 18, 2026

Uh oh!

openshift-ci bot commented Mar 18, 2026

Uh oh!

openshift-ci bot commented Mar 19, 2026

Uh oh!

openshift-ci bot commented Mar 19, 2026

Uh oh!

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

Uh oh!

Uh oh!

openshift-ci bot commented Mar 19, 2026

Uh oh!

openshift-ci bot commented Mar 20, 2026

Uh oh!

openshift-ci bot commented Mar 20, 2026

Uh oh!

openshift-ci bot commented Mar 21, 2026

Uh oh!

openshift-ci bot commented Mar 21, 2026

Uh oh!

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

Uh oh!

Uh oh!

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

Uh oh!

Uh oh!

openshift-ci bot commented Mar 23, 2026

Uh oh!

everettraven commented Apr 6, 2026

Uh oh!

everettraven commented Apr 6, 2026

Uh oh!

gcs278 commented Apr 6, 2026

Uh oh!

JoelSpeed commented Apr 7, 2026

Uh oh!

openshift-ci-robot commented Apr 7, 2026

Uh oh!

JoelSpeed commented Apr 7, 2026

Uh oh!

qodo-code-review bot commented Apr 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

everettraven commented Apr 7, 2026

Uh oh!

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

Uh oh!

Uh oh!

JoelSpeed commented Apr 7, 2026

Uh oh!

openshift-ci-robot commented Apr 7, 2026

Uh oh!

openshift-ci bot commented Apr 7, 2026

Uh oh!

openshift-ci-robot commented Apr 7, 2026

gcs278 commented Mar 18, 2026 •

edited

Loading

openshift-ci-robot commented Mar 18, 2026 •

edited by openshift-ci bot

Loading

coderabbitai bot commented Mar 18, 2026 •

edited

Loading

openshift-ci-robot commented Mar 19, 2026 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Mar 23, 2026 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Mar 23, 2026 •

edited by openshift-ci bot

Loading

qodo-code-review bot commented Apr 7, 2026 •

edited

Loading

gcs278 commented Apr 7, 2026 •

edited

Loading

JoelSpeed commented Apr 8, 2026 •

edited

Loading