OCPBUGS-126808: Enable OLMLifecycleAndCompatibility by default in version 5+

[joelanford]

Enables the OLMLifecycleAndCompatibility feature gate by default starting in OpenShift version 5.

The effective change here is removing this feature from 4.23.

The feature gate remains enabled for the existing SelfManaged, OKD, TechPreviewNoUpgrade, and DevPreviewNoUpgrade configurations.

[openshift-merge-bot]

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]

Hello @joelanford! 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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 266737b4-0fad-4b45-a522-06f56c626970

📥 Commits

Reviewing files that changed from the base of the PR and between 0cd9983 and 5c13b5e.

📒 Files selected for processing (8)

• features/features.go
• payload-manifests/featuregates/featureGate-4-SelfManagedHA-Default.yaml
• payload-manifests/featuregates/featureGate-4-SelfManagedHA-OKD.yaml
• payload-manifests/featuregates/featureGate-4-SelfManagedHA-TechPreviewNoUpgrade.yaml
• payload-manifests/featuregates/featureGate-5-10-SelfManagedHA-Default.yaml
• payload-manifests/featuregates/featureGate-5-10-SelfManagedHA-DevPreviewNoUpgrade.yaml
• payload-manifests/featuregates/featureGate-5-10-SelfManagedHA-OKD.yaml
• payload-manifests/featuregates/featureGate-5-10-SelfManagedHA-TechPreviewNoUpgrade.yaml

💤 Files with no reviewable changes (1)

• payload-manifests/featuregates/featureGate-4-SelfManagedHA-TechPreviewNoUpgrade.yaml

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

📝 Walkthrough

Walkthrough

FeatureGateOLMLifecycleAndCompatibility now enables versions 5 and later. Existing version 4 feature-gate manifests now target version 4 only and disable OLMLifecycleAndCompatibility. New manifests define feature-gate configurations for versions 5–10 across the Default, DevPreviewNoUpgrade, OKD, and TechPreviewNoUpgrade feature sets.

Priority: ➖ Normal

Merge Risk: ⚪ Minimal · up to 5c13b

The OLM lifecycle feature is disabled in all version-4 configurations and enabled from version 5 onward, which matches the agreed release plan. No blocking risk remains.

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the primary change: enabling OLMLifecycleAndCompatibility by default for version 5 and later.
Description check	✅ Passed	The description directly explains the feature-gate change, its version boundary, and the effect on existing configurations.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	The pull request changes one non-test Go declaration and eight FeatureGate YAML manifests. The changed Go file is not a _test.go file. The added line only changes feature-gate enablement and the pat…
Test Structure And Quality	✅ Passed	PASS: The pull request changes features/features.go and FeatureGate YAML manifests only. No Ginkgo test files or Ginkgo test constructs are added or modified, so the listed test-quality requirements…
Microshift Test Compatibility	✅ Passed	PASS: The pull request adds no Ginkgo tests. The authoritative diff changes features/features.go and FeatureGate YAML manifests only, so the MicroShift test-compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The pull request adds no Ginkgo e2e tests. The authoritative diff changes one feature configuration file and eight FeatureGate manifests. No added It(), Describe(), Context(), or When() test declarati…
Topology-Aware Scheduling Compatibility	✅ Passed	The pull request changes only feature-gate registration and FeatureGate payload resources. The diff adds no deployments, controllers, operator code, affinity, topology spread, replica, PDB, node selec…
Ote Binary Stdout Contract	✅ Passed	The pull request changes one declarative feature-gate condition in features/features.go and JSON feature-gate manifests. It adds no OTE binary entry point, suite setup, logging configuration, or std…
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The pull request adds no Ginkgo e2e tests. The authoritative diff contains one feature-gate registration change and FeatureGate YAML manifest changes only. No IPv4 assumptions or external connectivity…
No-Weak-Crypto	✅ Passed	PASS: The pull request changes only feature-gate logic and YAML manifests. The added inVersion(5, greaterThanOrEqual) condition and feature-gate lists contain no MD5, SHA-1, DES, 3DES, RC4, Blowfish…
Container-Privileges	✅ Passed	PASS. The pull request changes one feature-gate declaration and eight FeatureGate manifests. The manifests contain no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, se…
No-Sensitive-Data-In-Logs	✅ Passed	PASS: The pull request changes feature-gate conditions and manifests only. The authoritative diff adds no logging calls and no passwords, tokens, API keys, PII, session IDs, internal hostnames, or cus…

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

Warning

Some tools did not complete. Review the errors below.

🔧 golangci-lint (2.13.2)

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

[joelanford]

/retest

[everettraven]

@joelanford Any particular reason we want this only enabled in 5+?

[joelanford]

There's a large amount of extra work to do in the layered product ecosystem and pipeline to populate the data that this feature relies on. The BU would rather engineering focus efforts on OLMv1 MVP and the next round of update planner features rather than spend additional cycles making this feature worthwhile to enable in 4.23.

[openshift-ci-robot]

@joelanford: This pull request references Jira Issue OCPBUGS-126808, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

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

Details

In response to this:

Enables the OLMLifecycleAndCompatibility feature gate by default starting in OpenShift version 5.

The effective change here is removing this feature from 4.23.

The feature gate remains enabled for the existing SelfManaged, OKD, TechPreviewNoUpgrade, and DevPreviewNoUpgrade configurations.

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.

[joelanford]

/jira refresh

[openshift-ci-robot]

@joelanford: This pull request references Jira Issue OCPBUGS-126808, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

/jira refresh

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.

[joelanford]

/jira backport release-5.0

[openshift-ci-robot]

@joelanford: The following backport issues have been created:

• Jira Issue OCPBUGS-126809 for branch release-5.0

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-5.0

Details

In response to this:

/jira backport release-5.0

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-cherrypick-robot]

@openshift-ci-robot: once the present PR merges, I will cherry-pick it on top of release-5.0 in a new PR and assign it to you.

Details

In response to this:

@joelanford: The following backport issues have been created:

• Jira Issue OCPBUGS-126809 for branch release-5.0

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-5.0

In response to this:

/jira backport release-5.0

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.

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]

Is there something in Jira that tracks a BU decision to not ship this in 4.23?

[joelanford]

@JoelSpeed https://redhat.atlassian.net/browse/OCPSTRAT-2618?focusedCommentId=18564500

[joelanford]

/pipeline required

[openshift-merge-bot]

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

[joelanford]

/test e2e-aws-serial-2of2

[everettraven]

/lgtm
/approve

[redhat-chai-bot]

/override-sticky ci/prow/e2e-gcp

Automated triage: This failure appears unrelated to the PR changes.

Job classification: Eligible long-running GCP IPI end-to-end presubmit. The definition uses the openshift-e2e-gcp workflow with openshift-e2e-test, including GCP IPI install, cluster stabilization, conformance execution, and teardown.
Revision check: Prow run 0cd99835dbb34f0115fbb7a4b11844a9b5f62dcf; current PR HEAD 0cd99835dbb34f0115fbb7a4b11844a9b5f62dcf; match. Base SHA also matches 3a6e03c5a473d53330c6c77ec294eb4ac84fa6d9.
Execution status: Tests executed. e2e-gcp-openshift-e2e-test ran the conformance suite for 1h47m8s: 1 blocking failure, 2 informing failures, 2225 passed, 0 flaky, 2113 skipped. The blocking failure was [sig-node] Probing container should *not* be restarted with a tcp:8080 liveness probe [NodeConformance] [Conformance].
Completed supporting jobs: ci/prow/e2e-aws-ovn-hypershift, ci/prow/e2e-aws-ovn-hypershift-conformance, ci/prow/e2e-aws-serial-1of2, ci/prow/e2e-aws-serial-techpreview-1of2, ci/prow/e2e-azure, ci/prow/e2e-upgrade, and ci/prow/e2e-upgrade-out-of-change passed. Pending jobs: ci/prow/e2e-aws-serial-2of2, ci/prow/e2e-aws-serial-techpreview-2of2, and tide; pending checks were not used as positive signal.
Fleet-wide failure rate: The job was 52% successful over the last 14 days (13/25; Sippy current period 40%, 4/10), and this is already the GCP variant. The exact test was 99.39% successful globally over 14 days (14,320/14,408; 0 flakes) and 98.46% on GCP (2,435/2,473; 0 flakes). Sippy 5.1 current-period rates were 99.9% overall and 99.7% on GCP.
Open regressions: none found for this exact test in the relevant release.
Linked bugs: none. The explicit bug_tests association query returned no linked Jira bug.
Overlap assessment: The PR changes one feature-gate registration and eight FeatureGate manifests, enabling OLMLifecycleAndCompatibility for version 5+. It does not modify kubelet, container runtime, node, liveness-probe, or test code; no direct or indirect overlap with the failing node conformance surface was identified. The same exact test failed on a different openshift/api PR (#3028) in the same job on the same day.
Missing-coverage risk: low for this decision. The expensive GCP e2e job completed cluster provisioning and the full test execution, and the failure is isolated to an independent low-rate node liveness-probe failure. Other completed e2e and upgrade jobs provide additional signal; pending jobs are not relied upon.
Prior bot activity on this SHA: /test e2e-gcp was already triggered at 2026-09-22T12:53:59Z; no prior override for this job on this SHA. No additional retest is issued because the one-retest budget for this job/SHA is already used.
Rationale: The exact test fails outside this PR, the failure is in a node-level liveness-probe behavior unrelated to the feature-gate/API-manifest diff, and the current run executed tests on the live PR HEAD. Override is appropriate for this long-running e2e job.

If you disagree with this assessment, rerun the current job with /test e2e-gcp.

---

AI-generated. Review for accuracy.

[openshift-ci]

@redhat-chai-bot: Overrode contexts on behalf of redhat-chai-bot: ci/prow/e2e-gcp

These overrides will persist across retests on the current HEAD SHA. Pushing a new commit will clear them. Use /override-cancel to remove them.

Details

In response to this:

/override-sticky ci/prow/e2e-gcp

Automated triage: This failure appears unrelated to the PR changes.

Job classification: Eligible long-running GCP IPI end-to-end presubmit. The definition uses the openshift-e2e-gcp workflow with openshift-e2e-test, including GCP IPI install, cluster stabilization, conformance execution, and teardown.
Revision check: Prow run 0cd99835dbb34f0115fbb7a4b11844a9b5f62dcf; current PR HEAD 0cd99835dbb34f0115fbb7a4b11844a9b5f62dcf; match. Base SHA also matches 3a6e03c5a473d53330c6c77ec294eb4ac84fa6d9.
Execution status: Tests executed. e2e-gcp-openshift-e2e-test ran the conformance suite for 1h47m8s: 1 blocking failure, 2 informing failures, 2225 passed, 0 flaky, 2113 skipped. The blocking failure was [sig-node] Probing container should *not* be restarted with a tcp:8080 liveness probe [NodeConformance] [Conformance].
Completed supporting jobs: ci/prow/e2e-aws-ovn-hypershift, ci/prow/e2e-aws-ovn-hypershift-conformance, ci/prow/e2e-aws-serial-1of2, ci/prow/e2e-aws-serial-techpreview-1of2, ci/prow/e2e-azure, ci/prow/e2e-upgrade, and ci/prow/e2e-upgrade-out-of-change passed. Pending jobs: ci/prow/e2e-aws-serial-2of2, ci/prow/e2e-aws-serial-techpreview-2of2, and tide; pending checks were not used as positive signal.
Fleet-wide failure rate: The job was 52% successful over the last 14 days (13/25; Sippy current period 40%, 4/10), and this is already the GCP variant. The exact test was 99.39% successful globally over 14 days (14,320/14,408; 0 flakes) and 98.46% on GCP (2,435/2,473; 0 flakes). Sippy 5.1 current-period rates were 99.9% overall and 99.7% on GCP.
Open regressions: none found for this exact test in the relevant release.
Linked bugs: none. The explicit bug_tests association query returned no linked Jira bug.
Overlap assessment: The PR changes one feature-gate registration and eight FeatureGate manifests, enabling OLMLifecycleAndCompatibility for version 5+. It does not modify kubelet, container runtime, node, liveness-probe, or test code; no direct or indirect overlap with the failing node conformance surface was identified. The same exact test failed on a different openshift/api PR (#3028) in the same job on the same day.
Missing-coverage risk: low for this decision. The expensive GCP e2e job completed cluster provisioning and the full test execution, and the failure is isolated to an independent low-rate node liveness-probe failure. Other completed e2e and upgrade jobs provide additional signal; pending jobs are not relied upon.
Prior bot activity on this SHA: /test e2e-gcp was already triggered at 2026-09-22T12:53:59Z; no prior override for this job on this SHA. No additional retest is issued because the one-retest budget for this job/SHA is already used.
Rationale: The exact test fails outside this PR, the failure is in a node-level liveness-probe behavior unrelated to the feature-gate/API-manifest diff, and the current run executed tests on the live PR HEAD. Override is appropriate for this long-running e2e job.

If you disagree with this assessment, rerun the current job with /test e2e-gcp.

---

AI-generated. Review for accuracy.

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.

[redhat-chai-bot]

/override-sticky ci/prow/e2e-aws-ovn

Automated triage: This failure appears unrelated to the PR changes.

Job classification: Eligible long-running e2e/integration presubmit. The job uses the openshift-e2e-aws workflow with openshift-org-aws cluster profile and runs the common AWS+OVN end-to-end suite.
Revision check: run 0cd99835dbb34f0115fbb7a4b11844a9b5f62dcf; current PR HEAD 0cd99835dbb34f0115fbb7a4b11844a9b5f62dcf; match.
Execution status: Tests executed. The cluster installed successfully; the run executed 4,545 tests. The blocking failure was [Monitor:legacy-networking-invariants][sig-trt] excessive DNS lookup errors should not be encountered in disruption samples, which reported 57 DNS lookup timeout disruption events above the threshold of 50. The wrapper step and [sig-sippy] openshift-tests should work are derivative failures. The informing test [sig-cli] Workloads client test ROSA-OSD_CCS-ARO-ConnectedOnly-Author:yinzhou-Medium-71273-Medium-71275-Validate user is able to extract rhel8 and rhel9 oc from the ocp payload also failed but is non-blocking.
Completed supporting jobs: ci/prow/build, ci/prow/e2e-aws-ovn-hypershift, ci/prow/e2e-aws-ovn-hypershift-conformance, ci/prow/e2e-aws-serial-1of2, ci/prow/e2e-aws-serial-techpreview-1of2, ci/prow/e2e-azure, ci/prow/e2e-gcp, ci/prow/e2e-upgrade, ci/prow/e2e-upgrade-out-of-change, ci/prow/images, ci/prow/integration, ci/prow/lint, ci/prow/minor-images, ci/prow/okd-scos-images, ci/prow/unit, ci/prow/verify, ci/prow/verify-client-go, ci/prow/verify-crd-schema, ci/prow/verify-crdify, ci/prow/verify-deps, ci/prow/verify-feature-promotion, and ci/prow/verify-hypershift-integration passed. Pending: ci/prow/e2e-aws-serial-2of2, ci/prow/e2e-aws-serial-techpreview-2of2, and tide.
Fleet-wide failure rate: job 8/21 passed over the last 14 days (38.1%). The DNS monitor passed 97.3% globally and 97.8% on AWS over the last 7 days. The informing oc extraction test passed 0.0% on release 5.1 over the current period and is broadly broken outside this PR.
Open regressions: none found for the exact failing tests.
Linked bugs: none; no bug is linked through the failing-test association.
Overlap assessment: The PR changes feature-gate registration and feature-gate payload manifests, specifically enabling OLMLifecycleAndCompatibility for version 5+ and adjusting 4.x manifest coverage. It does not modify DNS, disruption monitoring, cluster provisioning, or the tested infrastructure surface. No plausible direct or indirect overlap with the observed DNS monitor failure was found.
Missing-coverage risk: Low for this failure. The job executed the end-to-end suite, the failure is an infrastructure DNS monitor threshold, and multiple completed e2e/platform checks passed. The remaining pending checks are recorded but are not used as positive signal.
Prior bot activity on this SHA: One targeted /test e2e-aws-ovn was already requested on 0cd99835dbb34f0115fbb7a4b11844a9b5f62dcf by openshift-merge-bot; no prior override for this job/SHA.
Rationale: The run spent 3h40m, completed cluster provisioning and test execution, and failed on a known fleet-wide DNS disruption monitor with 57 lookup-timeout events. The PR's API/feature-gate changes do not overlap the failure surface.

If you disagree with this assessment, rerun the current job with /test e2e-aws-ovn.

---

AI-generated. Review for accuracy.

[openshift-ci]

@redhat-chai-bot: Overrode contexts on behalf of redhat-chai-bot: ci/prow/e2e-aws-ovn

These overrides will persist across retests on the current HEAD SHA. Pushing a new commit will clear them. Use /override-cancel to remove them.

Details

In response to this:

/override-sticky ci/prow/e2e-aws-ovn

Automated triage: This failure appears unrelated to the PR changes.

Job classification: Eligible long-running e2e/integration presubmit. The job uses the openshift-e2e-aws workflow with openshift-org-aws cluster profile and runs the common AWS+OVN end-to-end suite.
Revision check: run 0cd99835dbb34f0115fbb7a4b11844a9b5f62dcf; current PR HEAD 0cd99835dbb34f0115fbb7a4b11844a9b5f62dcf; match.
Execution status: Tests executed. The cluster installed successfully; the run executed 4,545 tests. The blocking failure was [Monitor:legacy-networking-invariants][sig-trt] excessive DNS lookup errors should not be encountered in disruption samples, which reported 57 DNS lookup timeout disruption events above the threshold of 50. The wrapper step and [sig-sippy] openshift-tests should work are derivative failures. The informing test [sig-cli] Workloads client test ROSA-OSD_CCS-ARO-ConnectedOnly-Author:yinzhou-Medium-71273-Medium-71275-Validate user is able to extract rhel8 and rhel9 oc from the ocp payload also failed but is non-blocking.
Completed supporting jobs: ci/prow/build, ci/prow/e2e-aws-ovn-hypershift, ci/prow/e2e-aws-ovn-hypershift-conformance, ci/prow/e2e-aws-serial-1of2, ci/prow/e2e-aws-serial-techpreview-1of2, ci/prow/e2e-azure, ci/prow/e2e-gcp, ci/prow/e2e-upgrade, ci/prow/e2e-upgrade-out-of-change, ci/prow/images, ci/prow/integration, ci/prow/lint, ci/prow/minor-images, ci/prow/okd-scos-images, ci/prow/unit, ci/prow/verify, ci/prow/verify-client-go, ci/prow/verify-crd-schema, ci/prow/verify-crdify, ci/prow/verify-deps, ci/prow/verify-feature-promotion, and ci/prow/verify-hypershift-integration passed. Pending: ci/prow/e2e-aws-serial-2of2, ci/prow/e2e-aws-serial-techpreview-2of2, and tide.
Fleet-wide failure rate: job 8/21 passed over the last 14 days (38.1%). The DNS monitor passed 97.3% globally and 97.8% on AWS over the last 7 days. The informing oc extraction test passed 0.0% on release 5.1 over the current period and is broadly broken outside this PR.
Open regressions: none found for the exact failing tests.
Linked bugs: none; no bug is linked through the failing-test association.
Overlap assessment: The PR changes feature-gate registration and feature-gate payload manifests, specifically enabling OLMLifecycleAndCompatibility for version 5+ and adjusting 4.x manifest coverage. It does not modify DNS, disruption monitoring, cluster provisioning, or the tested infrastructure surface. No plausible direct or indirect overlap with the observed DNS monitor failure was found.
Missing-coverage risk: Low for this failure. The job executed the end-to-end suite, the failure is an infrastructure DNS monitor threshold, and multiple completed e2e/platform checks passed. The remaining pending checks are recorded but are not used as positive signal.
Prior bot activity on this SHA: One targeted /test e2e-aws-ovn was already requested on 0cd99835dbb34f0115fbb7a4b11844a9b5f62dcf by openshift-merge-bot; no prior override for this job/SHA.
Rationale: The run spent 3h40m, completed cluster provisioning and test execution, and failed on a known fleet-wide DNS disruption monitor with 57 lookup-timeout events. The PR's API/feature-gate changes do not overlap the failure surface.

If you disagree with this assessment, rerun the current job with /test e2e-aws-ovn.

---

AI-generated. Review for accuracy.

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]

/approve cancel
/hold

As far as I can tell the BU has not approved this to not ship in 4.23. In fact it appears they explicitly want this one in 4.23, this needs further discussion

[JoelSpeed]

/approve
/hold cancel

Discussion was had yesterday and BU are now aligned at all layers, per comment in slack we are going to drop this feature from 4.23

[JoelSpeed]

@redhat-chai-bot can you assess the two failing checks to see if they should be overridden?

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven, 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,everettraven]

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

[redhat-chai-bot]

@JoelSpeed — I've assessed both failing checks. Neither failure is related to the PR changes (enabling OLMLifecycleAndCompatibility by default in v5+). Both are eligible for override:

---

1. ci/prow/e2e-aws-ovn-techpreview — 1 blocking failure out of 2,284 passed tests.

• Failing test: [sig-network-edge][OCPFeatureGate:IngressControllerLBSecurityGroupsAWS] AWS NLB security groups managed through the IngressController spec effectuates an update to the security groups
• Assessment: This is an AWS NLB / IngressController security groups test in the sig-network-edge suite — completely unrelated to OLM feature gate changes. Mass failure check passed (9/10 threshold).

2. ci/prow/minor-e2e-upgrade-minor — MonitorTest failure (not a test case).

• Failure details: DNS disruption detected — 1 interval, 16 total seconds during a minor upgrade (5.0.0-rc.3 → 5.1.0-ci). Etcd probe failures occurred during upgrade revision changes, which is standard transient upgrade behavior.
• Assessment: Infrastructure-level monitor test failure unrelated to feature gate enablement. Mass failure check passed (1/10 threshold).

Both failures appear to be flaky/infrastructure issues. I'm unable to run /override from my current context, so these will need to be overridden manually.

---

AI-generated. Review for accuracy.

[JoelSpeed]

/override ci/prow/e2e-aws-ovn-techpreview
/override ci/prow/minor-e2e-upgrade-minor

[openshift-ci]

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-aws-ovn-techpreview, ci/prow/minor-e2e-upgrade-minor

Details

In response to this:

/override ci/prow/e2e-aws-ovn-techpreview
/override ci/prow/minor-e2e-upgrade-minor

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]

New changes are detected. LGTM label has been removed.

[joelanford]

/pipeline required

[openshift-merge-bot]

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

[openshift-ci]

@joelanford: 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/e2e-aws-serial-techpreview-1of2	5c13b5e	link	true	/test e2e-aws-serial-techpreview-1of2
ci/prow/e2e-aws-serial-techpreview-2of2	5c13b5e	link	true	/test e2e-aws-serial-techpreview-2of2
ci/prow/e2e-aws-ovn-techpreview	5c13b5e	link	true	/test e2e-aws-ovn-techpreview
ci/prow/minor-e2e-upgrade-minor	5c13b5e	link	true	/test minor-e2e-upgrade-minor

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.