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

gcs278 · 2026-06-02T23:12:16Z

Summary

Promote the GatewayAPIWithoutOLM feature gate to Default (GA) on release-4.20. This is the final PR needed to activate the no-OLM path for Gateway API on 4.20 — once merged, the Sail Library installation path replaces OLM-based Istio management in the next z-stream.

This is part of an approved SBAR to backport the Sail Library (noOLM) from 4.22 to 4.19–4.21.

Backport of #2772 (originally landed in 4.22).

Background

Gateway API on OCP 4.19–4.21 uses the Cluster Ingress Operator (CIO) to install Istio via OLM (OSSM operator). This path has several critical bugs:

OCPBUGS-92038: OSSM z-stream upgrades are blocked, preventing CVE fixes from being delivered
OCPBUGS-82147: OLM-related install failures
OCPBUGS-92041: Hardcoded catalog source breaks disconnected environments
OCPBUGS-92042: Gateway API fails on clusters without Marketplace capability

In OCP 4.22, NE-2286 replaced OLM with the Sail Library — CIO now installs Istio directly via embedded Helm charts. This feature shipped as GA behind the GatewayAPIWithoutOLM feature gate.

Rollout Plan

Phase 1 — Land code (gate OFF)

[release-4.20] OCPBUGS-85155: Backport GatewayAPIWithoutOLM feature gate as disabled #2871 — Add FG as disabled
[release-4.20] OCPBUGS-85155, OCPBUGS-87207: Enable Gateway API tests on vSphere and baremetal origin#31262 — Backport Gateway API test prerequisites
[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 origin#31322 — Backport noOLM test coverage and upgrade tests
[release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-82147, OCPBUGS-92041, OCPBUGS-92042: Replace OLM-based Istio install with Sail Library cluster-ingress-operator#1459 — Sail Library code lands, gate OFF

Phase 2 — TechPreview soak

[release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-82147, OCPBUGS-92041, OCPBUGS-92042: Promote GatewayAPIWithoutOLM feature gate to TechPreview #2874 — FG promotion to TechPreviewNoUpgrade
[release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-82147, OCPBUGS-92041, OCPBUGS-92042: Remove feature-set annotations from Sail Library RBAC Manifests cluster-ingress-operator#1497 — Remove feature-set annotation from Sail Library RBAC

Phase 3 — GA promotion

This PR — FG promotion to Default/GA, activates noOLM

Follow-up

Bump GWAPI CRDs to v1.4.1 OSSM 3.3.1 and Istio v1.28.5 cluster-ingress-operator#1455 — Bump GWAPI CRDs to v1.4.1 and Istio to v1.28.5

openshift-merge-bot · 2026-06-02T23:12:18Z

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-06-02T23:12:20Z

@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

Promote the GatewayAPIWithoutOLM feature gate to Default (enabled) on release-4.20. This activates the Sail Library installation path, replacing OLM-based Istio management for Gateway API.

This is a WIP — do not merge until the CIO noOLM backport and E2E tests are in place.

Implementation: openshift/cluster-ingress-operator#1459

Why

See the noOLM backport PR for full context. The primary driver is OCPBUGS-86778 which blocks all OSSM z-stream upgrades via OLM on 4.19-4.21, preventing CVE fixes from shipping.

🤖 Generated with Claude Code

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-02T23:12:20Z

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-06-02T23:12:21Z

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-02T23:12:24Z

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: 3dcdbeab-2d07-440e-82a9-17a2a20e536b

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

openshift-ci · 2026-06-25T02:10:14Z

@gcs278: This PR was included in a payload test run from openshift/origin#31322
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.20-upgrade-from-stable-4.19-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fdb1ad50-703a-11f1-8ca6-25963c2f707b-0

openshift-ci · 2026-06-25T02:10:23Z

@gcs278: This PR was included in a payload test run from openshift/origin#31322
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.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/02cda910-703b-11f1-8202-b9ab34f52f2b-0

openshift-ci · 2026-06-25T02:10:35Z

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

periodic-ci-openshift-release-main-nightly-4.20-upgrade-from-stable-4.19-e2e-metal-ipi-upgrade-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/09d8a390-703b-11f1-9aa0-93a802cd5146-0

openshift-ci · 2026-06-25T02:17:22Z

@gcs278: This PR was included in a payload test run from openshift/origin#31322
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.20-upgrade-from-stable-4.19-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fcafd840-703b-11f1-962a-ea9f67a1d4d1-0

openshift-ci · 2026-06-25T02:17:38Z

@gcs278: This PR was included in a payload test run from openshift/origin#31322
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.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/06111ed0-703c-11f1-940d-9b8efc8783d7-0

openshift-ci · 2026-06-25T02:17:55Z

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

periodic-ci-openshift-release-main-nightly-4.20-upgrade-from-stable-4.19-e2e-metal-ipi-upgrade-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/10ca2d30-703c-11f1-9e9a-43d6051ce295-0

openshift-ci-robot · 2026-06-25T19:03:14Z

@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

Promote the GatewayAPIWithoutOLM feature gate to Default (enabled) on release-4.20. This activates the Sail Library installation path, replacing OLM-based Istio management for Gateway API.

This is a WIP — do not merge until the CIO noOLM backport and E2E tests are in place.

Implementation: openshift/cluster-ingress-operator#1459

Why

See the noOLM backport PR for full context. The primary driver is OCPBUGS-86778 which blocks all OSSM z-stream upgrades via OLM on 4.19-4.21, preventing CVE fixes from shipping.

🤖 Generated with Claude Code

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:12Z

@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

Promote the GatewayAPIWithoutOLM feature gate to Default (enabled) on release-4.20. This activates the Sail Library installation path, replacing OLM-based Istio management for Gateway API.

This is a WIP — do not merge until the CIO noOLM backport and E2E tests are in place.

Implementation: openshift/cluster-ingress-operator#1459

Why

See the noOLM backport PR for full context. The primary driver is OCPBUGS-86778 which blocks all OSSM z-stream upgrades via OLM on 4.19-4.21, preventing CVE fixes from shipping.

🤖 Generated with Claude Code

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.

Enable the GatewayAPIWithoutOLM feature gate by default on release-4.20. This activates the Sail Library installation path, replacing OLM-based Istio management for Gateway API.

gcs278 · 2026-07-13T18:12:20Z

Should have some signal now:
/test verify-feature-promotion

gcs278 · 2026-07-14T17:36:57Z

/test verify-feature-promotion

gcs278 · 2026-07-14T18:02:23Z

/test verify-feature-promotion

gcs278 · 2026-07-14T21:48:55Z

/test verify-feature-promotion

openshift-ci-robot · 2026-07-14T23:57:19Z

@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 Closed (Done), 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

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 Closed (Done), 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.

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 Closed (Done), 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.

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 Closed (Done), 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.

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 Closed (Done), 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

Details

In response to this:

Summary

Promote the GatewayAPIWithoutOLM feature gate to Default (GA) on release-4.20. This is the final PR needed to activate the no-OLM path for Gateway API on 4.20 — once merged, the Sail Library installation path replaces OLM-based Istio management in the next z-stream.

This is part of an approved SBAR to backport the Sail Library (noOLM) from 4.22 to 4.19–4.21.

Backport of #2772 (originally landed in 4.22).

Background

Gateway API on OCP 4.19–4.21 uses the Cluster Ingress Operator (CIO) to install Istio via OLM (OSSM operator). This path has several critical bugs:

OCPBUGS-88295: OSSM z-stream upgrades are blocked, preventing CVE fixes from being delivered

OCPBUGS-82146: OLM-related install failures

OCPBUGS-78330: Hardcoded catalog source breaks disconnected environments

OCPBUGS-85550: Gateway API fails on clusters without Marketplace capability

In OCP 4.22, NE-2286 replaced OLM with the Sail Library — CIO now installs Istio directly via embedded Helm charts. This feature shipped as GA behind the GatewayAPIWithoutOLM feature gate.

Rollout Plan

Phase 1 — Land code (gate OFF)

[release-4.20] OCPBUGS-85155: Backport GatewayAPIWithoutOLM feature gate as disabled #2871 — Add FG as disabled

[release-4.20] OCPBUGS-85155, OCPBUGS-87207: Enable Gateway API tests on vSphere and baremetal origin#31262 — Backport Gateway API test prerequisites

[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 origin#31322 — Backport noOLM test coverage and upgrade tests

[release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-82147, OCPBUGS-92041, OCPBUGS-92042: Replace OLM-based Istio install with Sail Library cluster-ingress-operator#1459 — Sail Library code lands, gate OFF

Phase 2 — TechPreview soak

[release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-82147, OCPBUGS-92041, OCPBUGS-92042: Promote GatewayAPIWithoutOLM feature gate to TechPreview #2874 — FG promotion to TechPreviewNoUpgrade

[release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-82147, OCPBUGS-92041, OCPBUGS-92042: Remove feature-set annotations from Sail Library RBAC Manifests cluster-ingress-operator#1497 — Remove feature-set annotation from Sail Library RBAC

Phase 3 — GA promotion

This PR — FG promotion to Default/GA, activates noOLM

Follow-up

Bump GWAPI CRDs to v1.4.1 OSSM 3.3.1 and Istio v1.28.5 cluster-ingress-operator#1455 — Bump GWAPI CRDs to v1.4.1 and Istio to v1.28.5

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.

gcs278 · 2026-07-15T00:51:00Z

Taking out of draft to get CI spinning. There's been some concerning developments with the recent release OSSM 3.4 that make this a higher priority to get merged.

gcs278 · 2026-07-15T01:19:22Z

@JoelSpeed gangway is running - should be clearing our supported jobs (note that ipv6/dual is not supported) by the morning hopefully. Take a look when you get a chance.

JoelSpeed · 2026-07-15T07:48:54Z

/test verify-feature-promotion

JoelSpeed · 2026-07-15T09:27:24Z

/lgtm
/override ci/prow/verify-feature-promotion
/label backport-risk-assessed

openshift-ci · 2026-07-15T09:27:46Z

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

Details

In response to this:

/lgtm
/override ci/prow/verify-feature-promotion
/label backport-risk-assessed

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-07-15T09:28:14Z

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-15T09:28:17Z

[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

melvinjoseph86 · 2026-07-15T11:57:54Z

CC @rhamini3

gcs278 · 2026-07-15T12:15:07Z

/test e2e-aws-ovn-hypershift-conformance

gcs278 · 2026-07-15T13:53:51Z

/testwith openshift/api/release-4.21/e2e-upgrade-out-of-change openshift/origin#31391

gcs278 · 2026-07-15T14:03:59Z

unrelated failures
/test e2e-azure
/test e2e-aws-ovn-techpreview

For e2e-upgrade-out-of-change failure - that the GWAPI upgrade test failing due to a known issue, but we overrode it last time, it's only a pre-submit issue. I'll do a testwith just to prove it's working with the fix. Edit: Testwith passed showing it's passing with the fix.

gcs278 · 2026-07-15T14:07:07Z

/testwith openshift/api/release-4.20/e2e-upgrade-out-of-change openshift/origin#31391

gcs278 · 2026-07-15T14:07:15Z

/testwith openshift/api/release-4.20/e2e-upgrade-out-of-change openshift/origin#31391

gcs278 · 2026-07-15T17:16:41Z

known not related flake about http2 test failure:
/test e2e-aws-ovn-techpreview

openshift-ci · 2026-07-15T20:11:59Z

@gcs278: 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-feature-promotion	`4711957`	link	true	`/test verify-feature-promotion`
ci/prow/e2e-upgrade-out-of-change	`4711957`	link	true	`/test e2e-upgrade-out-of-change`

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-15T20:37:12Z

@JoelSpeed could I get an override for e2e-upgrade-out-of-change like you did in the 4.21 promotion PR please?

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

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

openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 5, 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

gcs278 force-pushed the backport-GatewayAPIWithoutOLM-4.20 branch from 5e17d9f to 1a86948 Compare June 25, 2026 02:15

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

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

openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jun 25, 2026

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

gcs278 mentioned this pull request Jul 2, 2026

[release-4.20] OCPBUGS-92038, OCPBUGS-92039, OCPBUGS-82147, OCPBUGS-92041, OCPBUGS-92042: Remove feature-set annotations from Sail Library RBAC Manifests openshift/cluster-ingress-operator#1497

Merged

NE-2480: Promote GatewayAPIWithoutOLM feature gate to Default

4711957

Enable the GatewayAPIWithoutOLM feature gate by default on release-4.20. This activates the Sail Library installation path, replacing OLM-based Istio management for Gateway API.

gcs278 marked this pull request as ready for review July 15, 2026 00:49

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

openshift-ci Bot requested review from JoelSpeed and everettraven July 15, 2026 00:49

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

openshift-ci Bot assigned gangwgr Jul 15, 2026

openshift-ci Bot assigned JoelSpeed Jul 15, 2026

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

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

Uh oh!

Conversation

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

Uh oh!

Summary

Background

Rollout Plan

Uh oh!

openshift-merge-bot Bot commented Jun 2, 2026

Uh oh!

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

Uh oh!

Summary

Why

Uh oh!

openshift-ci Bot commented Jun 2, 2026

Uh oh!

openshift-ci Bot commented Jun 2, 2026

Uh oh!

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

Uh oh!

Review skipped

Uh oh!

openshift-ci Bot commented Jun 25, 2026

Uh oh!

openshift-ci Bot commented Jun 25, 2026

Uh oh!

openshift-ci Bot commented Jun 25, 2026

Uh oh!

openshift-ci Bot commented Jun 25, 2026

Uh oh!

openshift-ci Bot commented Jun 25, 2026

Uh oh!

openshift-ci Bot commented Jun 25, 2026

Uh oh!

openshift-ci-robot commented Jun 25, 2026

Summary

Why

Uh oh!

openshift-ci-robot commented Jun 25, 2026

Summary

Why

Uh oh!

gcs278 commented Jul 13, 2026

Uh oh!

gcs278 commented Jul 14, 2026

Uh oh!

gcs278 commented Jul 14, 2026

Uh oh!

gcs278 commented Jul 14, 2026

Uh oh!

openshift-ci-robot commented Jul 14, 2026

Summary

Background

Rollout Plan

Uh oh!

gcs278 commented Jul 15, 2026

Uh oh!

gcs278 commented Jul 15, 2026

Uh oh!

JoelSpeed commented Jul 15, 2026

Uh oh!

JoelSpeed commented Jul 15, 2026

Uh oh!

openshift-ci Bot commented Jul 15, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 15, 2026

Uh oh!

openshift-ci Bot commented Jul 15, 2026

Uh oh!

melvinjoseph86 commented Jul 15, 2026

Uh oh!

gcs278 commented Jul 15, 2026

Uh oh!

gcs278 commented Jul 15, 2026

Uh oh!

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

Uh oh!

Uh oh!

gcs278 commented Jul 15, 2026

gcs278 commented Jun 2, 2026 •

edited

Loading

openshift-ci-robot commented Jun 2, 2026 •

edited by openshift-ci Bot

Loading

coderabbitai Bot commented Jun 2, 2026 •

edited

Loading

gcs278 commented Jul 15, 2026 •

edited

Loading