OCPBUGS-122251: Promote GCD to GA in 4.22

[patrickdillon]

Promotes GCD feature gate to GA in 4.22.

SBAR

[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 @patrickdillon! 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]

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 YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: b7e2f8d8-7026-4aed-988c-a301e3f54174

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

---

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

[JoelSpeed]

Will need to sort verify issues before we can continue here

[patrickdillon]

/retest-required

[patrickdillon]

After rebasing and regenerating, tests are passing. Ready for a second look, thanks!

[JoelSpeed]

@patrickdillon the feature promotion appears to be looking at all GCP tests, do we have specific periodics set up to test this feature?

[patrickdillon]

@patrickdillon the feature promotion appears to be looking at all GCP tests, do we have specific periodics set up to test this feature?

Ah good point, we currently only have presubmits on 4.22. I've just now opened a pr for the 4.22 periodics: openshift/release#85236

[patrickdillon]

/test verify-feature-promotion

we have some test runs now

[patrickdillon]

@JoelSpeed here are the tests for 4.22

https://prow.ci.openshift.org/job-history/gs/test-platform-results/logs/periodic-ci-openshift-release-main-ci-4.22-e2e-gcd-ovn

https://prow.ci.openshift.org/job-history/gs/test-platform-results/logs/periodic-ci-openshift-release-main-ci-4.22-e2e-gcd-ovn-techpreview

Not sure whether they are picked up by the verify-feature-promotion test. I suspect not. These are configured the same way as the later test jobs.

In any case, can you PTAL, as we are running up on the 4.22 deadline

[everettraven]

Have running jobs and the SBAR only required at least having some jobs. Jobs have some green signal and look to be passing installation so 👍 .

/override ci/prow/verify-feature-promotion

[openshift-ci]

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

Details

In response to this:

Have running jobs and the SBAR only required at least having some jobs. Jobs have some green signal and look to be passing installation so 👍 .

/override ci/prow/verify-feature-promotion

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[everettraven]

/lgtm

[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 e2e-vsphere-ovn

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven

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

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

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

Job classification: Eligible long-running e2e/integration presubmit. The Prow definition uses the hypershift-aws cluster profile and hypershift-aws-conformance workflow; the run provisions an ephemeral HyperShift cluster and executes conformance tests.
Revision check: run b02757d9023b78460bbae7809b1b598a5704aedf; current PR HEAD b02757d9023b78460bbae7809b1b598a5704aedf; event SHA matches; match.
Execution status: Tests executed. The run lasted 2h28m and completed 1935 passing, 1 blocking failure, 2 informing failures, 0 flaky, and 2128 skipped tests. The blocking test was [sig-node] Pod InPlace Resize Container burstable pods - extended resize with equivalents [MinimumKubeletVersion:1.34] [Conformance]. Its failure was caused by DNS resolver connection refusals while reading cgroup values: resolution of the AWS ELB hostname via 172.30.0.10:53 returned connection refused after 3 attempts.
Completed supporting jobs: ci/prow/e2e-aws-ovn-hypershift, ci/prow/e2e-upgrade, and ci/prow/e2e-upgrade-out-of-change passed. Build, unit, integration, lint, verify, image, and CRD checks also passed. Pending jobs, not counted as positive signal: ci/prow/e2e-aws-ovn, ci/prow/e2e-aws-ovn-techpreview, ci/prow/e2e-aws-serial-1of2, ci/prow/e2e-aws-serial-2of2, ci/prow/e2e-aws-serial-techpreview-1of2, ci/prow/e2e-aws-serial-techpreview-2of2, ci/prow/e2e-azure, ci/prow/e2e-gcp, ci/prow/e2e-vsphere-ovn, and tide.
Fleet-wide failure rate: Exact job: 2/3 passed (66.7%) in the last 14 days. Blocking test on release-4.22: 100.0% pass rate across 1404 runs, 0 failures, 0 flakes; AWS: 100.0% across 458 runs; HyperShift/external: 100.0% across 88 runs. No genuine release-4.22 failures were found for this exact test outside this run.
Open regressions: None found for the blocking test in release-4.22.
Linked bugs: None via an explicit bug_tests association for the blocking test. The two informing failures are pre-existing suite issues; they do not establish a PR-related failure.
Overlap assessment: The PR promotes GCD to GA and changes feature metadata plus generated CRD manifests. It does not touch kubelet in-place resize behavior, DNS, AWS networking, HyperShift provisioning, or CCO test inputs. No plausible direct or indirect overlap was found.
Missing-coverage risk: Low but nonzero. This job's conformance coverage is not fully green, but the suite executed for 1h20m58s, the sole blocking failure is a resolver/infrastructure error, and the completed HyperShift, upgrade, and non-e2e checks provide supporting signal. Pending checks were not used as evidence.
Prior bot activity on this SHA: The current job was triggered by openshift-merge-bot at 2026-09-18T12:32:54Z. No prior retest or override for this job appears on this SHA. The earlier verify-feature-promotion override was a different status context.
Rationale: The exact blocking failure is an isolated DNS connection-refused event during an otherwise extensive test run, with no PR overlap and a 100% fleet pass rate for the test on the relevant release/platform dimensions. No recorded outage overlapped the 13:10–13:25 failure window; later Prow/AWS/Boskos outages began after the test failure.

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

---

AI-generated. Review for accuracy.

[openshift-ci]

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

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-hypershift-conformance

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

Job classification: Eligible long-running e2e/integration presubmit. The Prow definition uses the hypershift-aws cluster profile and hypershift-aws-conformance workflow; the run provisions an ephemeral HyperShift cluster and executes conformance tests.
Revision check: run b02757d9023b78460bbae7809b1b598a5704aedf; current PR HEAD b02757d9023b78460bbae7809b1b598a5704aedf; event SHA matches; match.
Execution status: Tests executed. The run lasted 2h28m and completed 1935 passing, 1 blocking failure, 2 informing failures, 0 flaky, and 2128 skipped tests. The blocking test was [sig-node] Pod InPlace Resize Container burstable pods - extended resize with equivalents [MinimumKubeletVersion:1.34] [Conformance]. Its failure was caused by DNS resolver connection refusals while reading cgroup values: resolution of the AWS ELB hostname via 172.30.0.10:53 returned connection refused after 3 attempts.
Completed supporting jobs: ci/prow/e2e-aws-ovn-hypershift, ci/prow/e2e-upgrade, and ci/prow/e2e-upgrade-out-of-change passed. Build, unit, integration, lint, verify, image, and CRD checks also passed. Pending jobs, not counted as positive signal: ci/prow/e2e-aws-ovn, ci/prow/e2e-aws-ovn-techpreview, ci/prow/e2e-aws-serial-1of2, ci/prow/e2e-aws-serial-2of2, ci/prow/e2e-aws-serial-techpreview-1of2, ci/prow/e2e-aws-serial-techpreview-2of2, ci/prow/e2e-azure, ci/prow/e2e-gcp, ci/prow/e2e-vsphere-ovn, and tide.
Fleet-wide failure rate: Exact job: 2/3 passed (66.7%) in the last 14 days. Blocking test on release-4.22: 100.0% pass rate across 1404 runs, 0 failures, 0 flakes; AWS: 100.0% across 458 runs; HyperShift/external: 100.0% across 88 runs. No genuine release-4.22 failures were found for this exact test outside this run.
Open regressions: None found for the blocking test in release-4.22.
Linked bugs: None via an explicit bug_tests association for the blocking test. The two informing failures are pre-existing suite issues; they do not establish a PR-related failure.
Overlap assessment: The PR promotes GCD to GA and changes feature metadata plus generated CRD manifests. It does not touch kubelet in-place resize behavior, DNS, AWS networking, HyperShift provisioning, or CCO test inputs. No plausible direct or indirect overlap was found.
Missing-coverage risk: Low but nonzero. This job's conformance coverage is not fully green, but the suite executed for 1h20m58s, the sole blocking failure is a resolver/infrastructure error, and the completed HyperShift, upgrade, and non-e2e checks provide supporting signal. Pending checks were not used as evidence.
Prior bot activity on this SHA: The current job was triggered by openshift-merge-bot at 2026-09-18T12:32:54Z. No prior retest or override for this job appears on this SHA. The earlier verify-feature-promotion override was a different status context.
Rationale: The exact blocking failure is an isolated DNS connection-refused event during an otherwise extensive test run, with no PR overlap and a 100% fleet pass rate for the test on the relevant release/platform dimensions. No recorded outage overlapped the 13:10–13:25 failure window; later Prow/AWS/Boskos outages began after the test failure.

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

---

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-azure

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

Job classification: Eligible long-running Azure IPI end-to-end presubmit. The openshift-e2e-azure workflow provisions an Azure cluster and runs openshift-e2e-test; this run lasted 3h6m25s and executed the test suite.

Revision check: run b02757d9023b78460bbae7809b1b598a5704aedf; current PR HEAD b02757d9023b78460bbae7809b1b598a5704aedf; match.

Execution status: Tests executed. The suite reported 4 blocking failures, 1 informing failure, 2,072 passed, 0 flaky, and 2,001 skipped. The test phase ran for 1h47m3s. The log records repeated API, service-load-balancer, metrics, and image-registry disruption samples with i/o timeout / 503 Service Unavailable, including panics while retrieving kubernetes.default.

Completed supporting jobs: e2e-aws-ovn-hypershift, e2e-aws-serial-1of2, e2e-upgrade, e2e-upgrade-out-of-change, plus the successful build, integration, lint, unit, verify, verify-client-go, verify-crd-schema, verify-crdify, verify-deps, images, and okd-scos-images checks. Pending separately: e2e-aws-ovn, e2e-aws-ovn-techpreview, e2e-aws-serial-2of2, e2e-aws-serial-techpreview-1of2, e2e-gcp, and tide. e2e-vsphere-ovn was also failed and was not used as positive signal.

Fleet-wide failure rate: The job pass rate is 33.3% over the recent fleet sample (2 passed / 4 failed). [Feature:NetworkSegmentation][ovn-kubernetes-ote][sig-network] Network Segmentation: services on a user defined primary network should be reachable through their cluster IP, node port and load balancer L2 primary UDN with custom network, cluster-networked pods, NodePort service [Suite:openshift/conformance/parallel] has 0.0% pass rate globally (0/1,262) and on Azure (0/212). [sig-cli] Kubectl client Simple pod should support exec is 100.0% globally and on Azure; [sig-node] [DRA] kubelet [Feature:DynamicResourceAllocation] rolling update [KubeletMinVersion:1.33] is 99.9% globally and 99.6% on Azure. [sig-storage] In-tree Volumes [Driver: hostPathSymlink] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support two pods which have the same volume definition had only this run in the available history. The informing [sig-storage] In-tree Volumes [Driver: azure-file] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with pvc data source (ROX mode) had no tracked rate.

Open regressions: None found for the failing tests in the relevant Component Readiness data.

Linked bugs: None. No Jira bug was linked to the failing tests through the test association.

Overlap assessment: The PR promotes a feature gate and updates generated CRD manifests; it does not modify Azure provisioning, networking, API-server availability, CLI exec, DRA rolling-update, or storage-driver implementation. The exact failures correlate with multi-backend Azure connectivity disruption and a fleet-wide NetworkSegmentation failure, not with the changed files or the promoted feature gate.

Missing-coverage risk: Low for this decision because the job executed 2,072 tests, the failures have independent fleet/infrastructure evidence, and completed same-HEAD build, unit, integration, verification, upgrade, and multiple e2e checks provide additional signal. Pending checks remain pending and were not counted as positive signal.

Prior bot activity on this SHA: /test e2e-azure was already triggered at 2026-09-18T12:32:54Z; no prior sticky override for this context was recorded. Do not retest again under the one-retest-per-job-per-SHA limit.

Rationale: Override is appropriate for this executed, long-running e2e failure: one blocking test is demonstrably fleet-wide broken, while the other blocking failures occurred amid repeated API/network disruptions and timeouts. The failure is not attributable to PR #3034.

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

---

AI-generated. Review for accuracy.

[openshift-ci]

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

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-azure

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

Job classification: Eligible long-running Azure IPI end-to-end presubmit. The openshift-e2e-azure workflow provisions an Azure cluster and runs openshift-e2e-test; this run lasted 3h6m25s and executed the test suite.

Revision check: run b02757d9023b78460bbae7809b1b598a5704aedf; current PR HEAD b02757d9023b78460bbae7809b1b598a5704aedf; match.

Execution status: Tests executed. The suite reported 4 blocking failures, 1 informing failure, 2,072 passed, 0 flaky, and 2,001 skipped. The test phase ran for 1h47m3s. The log records repeated API, service-load-balancer, metrics, and image-registry disruption samples with i/o timeout / 503 Service Unavailable, including panics while retrieving kubernetes.default.

Completed supporting jobs: e2e-aws-ovn-hypershift, e2e-aws-serial-1of2, e2e-upgrade, e2e-upgrade-out-of-change, plus the successful build, integration, lint, unit, verify, verify-client-go, verify-crd-schema, verify-crdify, verify-deps, images, and okd-scos-images checks. Pending separately: e2e-aws-ovn, e2e-aws-ovn-techpreview, e2e-aws-serial-2of2, e2e-aws-serial-techpreview-1of2, e2e-gcp, and tide. e2e-vsphere-ovn was also failed and was not used as positive signal.

Fleet-wide failure rate: The job pass rate is 33.3% over the recent fleet sample (2 passed / 4 failed). [Feature:NetworkSegmentation][ovn-kubernetes-ote][sig-network] Network Segmentation: services on a user defined primary network should be reachable through their cluster IP, node port and load balancer L2 primary UDN with custom network, cluster-networked pods, NodePort service [Suite:openshift/conformance/parallel] has 0.0% pass rate globally (0/1,262) and on Azure (0/212). [sig-cli] Kubectl client Simple pod should support exec is 100.0% globally and on Azure; [sig-node] [DRA] kubelet [Feature:DynamicResourceAllocation] rolling update [KubeletMinVersion:1.33] is 99.9% globally and 99.6% on Azure. [sig-storage] In-tree Volumes [Driver: hostPathSymlink] [Testpattern: Generic Ephemeral-volume (default fs) (immediate-binding)] ephemeral should support two pods which have the same volume definition had only this run in the available history. The informing [sig-storage] In-tree Volumes [Driver: azure-file] [Testpattern: Dynamic PV (block volmode)] provisioning should provision storage with pvc data source (ROX mode) had no tracked rate.

Open regressions: None found for the failing tests in the relevant Component Readiness data.

Linked bugs: None. No Jira bug was linked to the failing tests through the test association.

Overlap assessment: The PR promotes a feature gate and updates generated CRD manifests; it does not modify Azure provisioning, networking, API-server availability, CLI exec, DRA rolling-update, or storage-driver implementation. The exact failures correlate with multi-backend Azure connectivity disruption and a fleet-wide NetworkSegmentation failure, not with the changed files or the promoted feature gate.

Missing-coverage risk: Low for this decision because the job executed 2,072 tests, the failures have independent fleet/infrastructure evidence, and completed same-HEAD build, unit, integration, verification, upgrade, and multiple e2e checks provide additional signal. Pending checks remain pending and were not counted as positive signal.

Prior bot activity on this SHA: /test e2e-azure was already triggered at 2026-09-18T12:32:54Z; no prior sticky override for this context was recorded. Do not retest again under the one-retest-per-job-per-SHA limit.

Rationale: Override is appropriate for this executed, long-running e2e failure: one blocking test is demonstrably fleet-wide broken, while the other blocking failures occurred amid repeated API/network disruptions and timeouts. The failure is not attributable to PR #3034.

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

---

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.

[patrickdillon]

/jira cherrypick OCPBUGS-114620

[openshift-ci-robot]

@patrickdillon: Detected clone of Jira Issue OCPBUGS-114620 with correct target version. Will retitle the PR to link to the clone.
/retitle OCPBUGS-122251: Promote GCD to GA in 4.22

Details

In response to this:

/jira cherrypick OCPBUGS-114620

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.

[patrickdillon]

/verified by e2e & unit

[openshift-ci-robot]

@patrickdillon: This pull request references Jira Issue OCPBUGS-122251, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-114620 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-114620 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
• bug has dependents

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

Details

In response to this:

Promotes GCD feature gate to GA in 4.22.

SBAR

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]

@patrickdillon: This PR has been marked as verified by e2e & unit.

Details

In response to this:

/verified by e2e & unit

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.

[everettraven]

/label backport-risk-assessed

/override ci/prow/e2e-vsphere-ovn

[openshift-ci]

@everettraven: Overrode contexts on behalf of everettraven: ci/prow/e2e-vsphere-ovn

Details

In response to this:

/label backport-risk-assessed

/override ci/prow/e2e-vsphere-ovn

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]

@patrickdillon: 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-vsphere-ovn	b02757d	link	true	/test e2e-vsphere-ovn
ci/prow/e2e-aws-ovn-hypershift-conformance	b02757d	link	true	/test e2e-aws-ovn-hypershift-conformance
ci/prow/e2e-azure	b02757d	link	true	/test e2e-azure

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci-robot]

@patrickdillon: Jira Issue OCPBUGS-122251: Some pull requests linked via external trackers have merged:

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

• openshift/installer#10871 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-122251 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:

Promotes GCD feature gate to GA in 4.22.

SBAR

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

Fix included in release 4.22.0-0.nightly-2026-09-22-171205