[release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-82147, OCPBUGS-92041, OCPBUGS-92042: Promote GatewayAPIWithoutOLM feature gate to TechPreview by gcs278 · Pull Request #2874 · openshift/api

gcs278 · 2026-06-03T21:23:25Z

Summary

Enable the GatewayAPIWithoutOLM feature gate in DevPreviewNoUpgrade and TechPreviewNoUpgrade feature sets on release-4.20 to allow CI soak before GA promotion.

This is an intermediate step before promoting to Default (GA) in PR #2869.

Merge Order

This should be merged after the Sail Library backport PR lands in cluster-ingress-operator (openshift/cluster-ingress-operator#1459) and before the GA promotion PR (#2869).

openshift-merge-bot · 2026-06-03T21:23:28Z

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 · 2026-06-03T21:23:30Z

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-robot · 2026-06-03T21:23:30Z

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

Details

In response to this:

Summary

Enable the GatewayAPIWithoutOLM feature gate in DevPreviewNoUpgrade and TechPreviewNoUpgrade feature sets on release-4.20 to allow CI soak before GA promotion.

This is an intermediate step before promoting to Default (GA) in PR #2869.

Merge Order

This should be merged after the Sail Library backport PR lands in cluster-ingress-operator (openshift/cluster-ingress-operator#1459) and before the GA promotion PR (#2869).

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

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-06-03T21:23:33Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 98eb7d57-5712-488f-bab8-225aa9c320a8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

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

…TechPreview Enable the GatewayAPIWithoutOLM feature gate in DevPreviewNoUpgrade and TechPreviewNoUpgrade feature sets to allow CI soak before GA promotion.

openshift-ci-robot · 2026-06-25T19:02:44Z

@gcs278: This pull request references Jira Issue OCPBUGS-92038, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-88295 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-88295 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

Requesting review from QA contact:
/cc @melvinjoseph86

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-92039, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-88297 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-88297 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (iamin@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-92040, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-82146 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-82146 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (iamin@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-92041, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-78330 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-78330 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (iamin@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-92042, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-85550 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-85550 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

Requesting review from QA contact:
/cc @melvinjoseph86

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

Enable the GatewayAPIWithoutOLM feature gate in DevPreviewNoUpgrade and TechPreviewNoUpgrade feature sets on release-4.20 to allow CI soak before GA promotion.

This is an intermediate step before promoting to Default (GA) in PR #2869.

Merge Order

This should be merged after the Sail Library backport PR lands in cluster-ingress-operator (openshift/cluster-ingress-operator#1459) and before the GA promotion PR (#2869).

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-06-25T19:16:06Z

@gcs278: This pull request references Jira Issue OCPBUGS-92038, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-88295 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-88295 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

Requesting review from QA contact:
/cc @melvinjoseph86

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-92039, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-88297 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-88297 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (iamin@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-82147, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-82146 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-82146 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (iamin@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-92041, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-78330 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-78330 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (iamin@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-92042, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.20.z) matches configured target version for branch (4.20.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-85550 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-85550 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

Requesting review from QA contact:
/cc @melvinjoseph86

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

Enable the GatewayAPIWithoutOLM feature gate in DevPreviewNoUpgrade and TechPreviewNoUpgrade feature sets on release-4.20 to allow CI soak before GA promotion.

This is an intermediate step before promoting to Default (GA) in PR #2869.

Merge Order

This should be merged after the Sail Library backport PR lands in cluster-ingress-operator (openshift/cluster-ingress-operator#1459) and before the GA promotion PR (#2869).

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.

JoelSpeed · 2026-07-06T08:06:30Z

/lgtm
/label backport-risk-assessed

openshift-merge-bot · 2026-07-06T08:07:54Z

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

openshift-ci · 2026-07-06T08:08:08Z

[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

gcs278 · 2026-07-06T17:15:39Z

unrelated hypershift failure (not techpreview):
/test e2e-aws-ovn-hypershift

openshift-ci · 2026-07-06T18:26:43Z

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

rhamini3 · 2026-07-06T20:15:56Z

tested on a 4.20 TP cluster, GatewayAPI works as intended

    enabled:
    - name: GCPCustomAPIEndpoints
    - name: GCPCustomAPIEndpointsInstall
    - name: GatewayAPI
    - name: GatewayAPIController
    - name: GatewayAPIWithoutOLM
    
% oc get gc -o yaml
apiVersion: v1
items:
- apiVersion: gateway.networking.k8s.io/v1
  kind: GatewayClass
  metadata:
    creationTimestamp: "2026-07-06T19:55:05Z"
    finalizers:
    - openshift.io/ingress-operator-sail-finalizer
    generation: 1
    name: openshift-default
    resourceVersion: "40049"
    uid: c25ea3a9-0ee5-481e-9ff2-a8a739bba6c3
  spec:
    controllerName: openshift.io/gateway-controller/v1
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:55:11Z"
      message: Handled by Istio controller
      observedGeneration: 1
      reason: Accepted
      status: "True"
      type: Accepted
    - lastTransitionTime: "2026-07-06T19:55:07Z"
      message: istiod v1.26.2 installed
      observedGeneration: 1
      reason: Installed
      status: "True"
      type: ControllerInstalled
    - lastTransitionTime: "2026-07-06T19:55:07Z"
      message: CRDs updated by CIO
      observedGeneration: 1
      reason: ManagedByCIO
      status: "True"
      type: CRDsReady
kind: List
metadata:
  resourceVersion: ""

% oc -n openshift-ingress get gateway
NAME      CLASS               ADDRESS                                                                 PROGRAMMED   AGE
gateway   openshift-default   aaa17c9584db24ea5b99e3851b145d00-30054963.us-east-1.elb.amazonaws.com   True         73s

HTTPRoute

  status:
    parents:
    - conditions:
      - lastTransitionTime: "2026-07-06T20:06:36Z"
        message: Route was valid
        observedGeneration: 1
        reason: Accepted
        status: "True"
        type: Accepted
      - lastTransitionTime: "2026-07-06T20:06:36Z"
        message: All references resolved
        observedGeneration: 1
        reason: ResolvedRefs
        status: "True"
        type: ResolvedRefs
      controllerName: openshift.io/gateway-controller/v1
      parentRef:
        group: gateway.networking.k8s.io
        kind: Gateway
        name: gateway
        namespace: openshift-ingress
kind: List
metadata:
  resourceVersion: ""

/verified by @rhamini3

openshift-ci-robot · 2026-07-06T20:16:09Z

@rhamini3: This PR has been marked as verified by @rhamini3.

Details

In response to this:

tested on a 4.20 TP cluster, GatewayAPI works as intended

   enabled:
   - name: GCPCustomAPIEndpoints
   - name: GCPCustomAPIEndpointsInstall
   - name: GatewayAPI
   - name: GatewayAPIController
   - name: GatewayAPIWithoutOLM
   
% oc get gc -o yaml
apiVersion: v1
items:
- apiVersion: gateway.networking.k8s.io/v1
 kind: GatewayClass
 metadata:
   creationTimestamp: "2026-07-06T19:55:05Z"
   finalizers:
   - openshift.io/ingress-operator-sail-finalizer
   generation: 1
   name: openshift-default
   resourceVersion: "40049"
   uid: c25ea3a9-0ee5-481e-9ff2-a8a739bba6c3
 spec:
   controllerName: openshift.io/gateway-controller/v1
 status:
   conditions:
   - lastTransitionTime: "2026-07-06T19:55:11Z"
     message: Handled by Istio controller
     observedGeneration: 1
     reason: Accepted
     status: "True"
     type: Accepted
   - lastTransitionTime: "2026-07-06T19:55:07Z"
     message: istiod v1.26.2 installed
     observedGeneration: 1
     reason: Installed
     status: "True"
     type: ControllerInstalled
   - lastTransitionTime: "2026-07-06T19:55:07Z"
     message: CRDs updated by CIO
     observedGeneration: 1
     reason: ManagedByCIO
     status: "True"
     type: CRDsReady
kind: List
metadata:
 resourceVersion: ""

% oc -n openshift-ingress get gateway
NAME      CLASS               ADDRESS                                                                 PROGRAMMED   AGE
gateway   openshift-default   aaa17c9584db24ea5b99e3851b145d00-30054963.us-east-1.elb.amazonaws.com   True         73s

HTTPRoute

 status:
   parents:
   - conditions:
     - lastTransitionTime: "2026-07-06T20:06:36Z"
       message: Route was valid
       observedGeneration: 1
       reason: Accepted
       status: "True"
       type: Accepted
     - lastTransitionTime: "2026-07-06T20:06:36Z"
       message: All references resolved
       observedGeneration: 1
       reason: ResolvedRefs
       status: "True"
       type: ResolvedRefs
     controllerName: openshift.io/gateway-controller/v1
     parentRef:
       group: gateway.networking.k8s.io
       kind: Gateway
       name: gateway
       namespace: openshift-ingress
kind: List
metadata:
 resourceVersion: ""

/verified by @rhamini3

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-07-06T20:20:34Z

@gcs278: Jira Issue OCPBUGS-92038: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

openshift/api#2869 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-92038 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Jira Issue OCPBUGS-92039: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

openshift/api#2869 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-92039 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Jira Issue OCPBUGS-82147: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

openshift/api#2869 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-82147 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Jira Issue OCPBUGS-92041: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

openshift/api#2869 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-92041 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Jira Issue OCPBUGS-92042: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

openshift/api#2869 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-92042 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Details

In response to this:

Summary

Enable the GatewayAPIWithoutOLM feature gate in DevPreviewNoUpgrade and TechPreviewNoUpgrade feature sets on release-4.20 to allow CI soak before GA promotion.

This is an intermediate step before promoting to Default (GA) in PR #2869.

Merge Order

This should be merged after the Sail Library backport PR lands in cluster-ingress-operator (openshift/cluster-ingress-operator#1459) and before the GA promotion PR (#2869).

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 added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 3, 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 Jun 3, 2026

openshift-ci Bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 3, 2026

gcs278 mentioned this pull request Jun 22, 2026

[release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-82147, OCPBUGS-92041, OCPBUGS-92042, OCPBUGS-92043, OCPBUGS-92044, OCPBUGS-92045: Backport noOLM Gateway API test coverage and upgrade tests openshift/origin#31322

Merged

[release-4.20] NE-2480: Promote GatewayAPIWithoutOLM feature gate to …

524067d

…TechPreview Enable the GatewayAPIWithoutOLM feature gate in DevPreviewNoUpgrade and TechPreviewNoUpgrade feature sets to allow CI soak before GA promotion.

gcs278 force-pushed the backport-GatewayAPIWithoutOLM-TP-4.20 branch from 37cdf46 to 524067d Compare June 25, 2026 02:13

gcs278 changed the title ~~[release-4.20] NE-2480: Promote GatewayAPIWithoutOLM feature gate to TechPreview~~ [release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-92040, OCPBUGS-92041, OCPBUGS-92042: Promote GatewayAPIWithoutOLM feature gate to TechPreview Jun 25, 2026

openshift-ci-robot added the jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. label Jun 25, 2026

openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jun 25, 2026

openshift-ci Bot requested a review from melvinjoseph86 June 25, 2026 19:02

gcs278 marked this pull request as ready for review July 3, 2026 20:42

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 3, 2026

openshift-ci Bot requested review from JoelSpeed and everettraven July 3, 2026 20:42

openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jul 6, 2026

openshift-ci Bot assigned gangwgr and JoelSpeed Jul 6, 2026

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

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

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

openshift-merge-bot Bot merged commit 7df7d59 into openshift:release-4.20 Jul 6, 2026
24 checks passed

Uh oh!

Conversation

gcs278 commented Jun 3, 2026

Summary

Merge Order

Uh oh!

openshift-merge-bot Bot commented Jun 3, 2026

Uh oh!

openshift-ci Bot commented Jun 3, 2026

Uh oh!

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

Uh oh!

Summary

Merge Order

Uh oh!

openshift-ci Bot commented Jun 3, 2026

Uh oh!

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

Uh oh!

Review skipped

Uh oh!

openshift-ci-robot commented Jun 25, 2026

Summary

Merge Order

Uh oh!

openshift-ci-robot commented Jun 25, 2026

Summary

Merge Order

Uh oh!

JoelSpeed commented Jul 6, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 6, 2026

Uh oh!

openshift-ci Bot commented Jul 6, 2026

Uh oh!

gcs278 commented Jul 6, 2026

Uh oh!

openshift-ci Bot commented Jul 6, 2026

Uh oh!

rhamini3 commented Jul 6, 2026

Uh oh!

openshift-ci-robot commented Jul 6, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Jul 6, 2026

Summary

Merge Order

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

openshift-ci-robot commented Jun 3, 2026 •

edited by openshift-ci Bot

Loading

coderabbitai Bot commented Jun 3, 2026 •

edited

Loading