updating rhoe 4.22 jobs for preflight and operator-pipelines to use f…

[acornett21]

…ast channel

Summary by CodeRabbit

This pull request updates the OpenShift CI configuration for Red Hat OpenShift Ecosystem (RHOE) 4.22 components to use the fast release channel instead of candidate or nightly streams.

Affected CI configurations:

The changes impact three main RHOE component repositories:

1. Certified Operators Preprod - Updates the 4.22 CI configuration to target the fast release channel when building against OCP
2. Certified Operators Prod - Updates the 4.22 production CI configuration similarly to use the fast channel
3. OpenShift Preflight - Removes the 4.21 variant configuration entirely and updates the 4.22 variant to use the fast channel

Practical impact:

The CI/CD pipelines for these RHOE components will now validate against the fast release channel of OpenShift 4.22, rather than the candidate/nightly streams, ensuring compatibility with the more stable fast-track releases.

[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: eb2d1bd1-618d-4280-bd9d-eeaf799c4205

📥 Commits

Reviewing files that changed from the base of the PR and between dcaae87 and 494beb0.

⛔ Files ignored due to path filters (3)

• ci-operator/jobs/redhat-openshift-ecosystem/certified-operators-preprod/redhat-openshift-ecosystem-certified-operators-preprod-ocp-4.22-periodics.yaml is excluded by !ci-operator/jobs/**
• ci-operator/jobs/redhat-openshift-ecosystem/certified-operators-prod/redhat-openshift-ecosystem-certified-operators-prod-ocp-4.22-periodics.yaml is excluded by !ci-operator/jobs/**
• ci-operator/jobs/redhat-openshift-ecosystem/openshift-preflight/redhat-openshift-ecosystem-openshift-preflight-main-presubmits.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (4)

• ci-operator/config/redhat-openshift-ecosystem/certified-operators-preprod/redhat-openshift-ecosystem-certified-operators-preprod-ocp-4.22.yaml
• ci-operator/config/redhat-openshift-ecosystem/certified-operators-prod/redhat-openshift-ecosystem-certified-operators-prod-ocp-4.22.yaml
• ci-operator/config/redhat-openshift-ecosystem/openshift-preflight/redhat-openshift-ecosystem-openshift-preflight-main__4.21.yaml
• ci-operator/config/redhat-openshift-ecosystem/openshift-preflight/redhat-openshift-ecosystem-openshift-preflight-main__4.22.yaml

💤 Files with no reviewable changes (1)

• ci-operator/config/redhat-openshift-ecosystem/openshift-preflight/redhat-openshift-ecosystem-openshift-preflight-main__4.21.yaml

---

Walkthrough

CI operator configurations for certified operators and OpenShift preflight are updated to standardize the releases.latest channel definition to fast across OCP 4.22 variants, replacing the prior candidate selector with stream: nightly configuration.

Changes

Release channel standardization to fast

Layer / File(s)	Summary
Certified operators 4.22 release channel updates ci-operator/config/redhat-openshift-ecosystem/certified-operators-preprod/redhat-openshift-ecosystem-certified-operators-preprod-ocp-4.22.yaml, ci-operator/config/redhat-openshift-ecosystem/certified-operators-prod/redhat-openshift-ecosystem-certified-operators-prod-ocp-4.22.yaml	Both preprod and prod certified operators OCP 4.22 configurations update releases.latest to specify channel: fast, replacing the prior candidate/nightly stream definition.
OpenShift preflight 4.22 release channel update ci-operator/config/redhat-openshift-ecosystem/openshift-preflight/redhat-openshift-ecosystem-openshift-preflight-main__4.22.yaml	OpenShift preflight main branch OCP 4.22 configuration updates releases.latest to use channel: fast instead of the prior candidate selector with product: ocp and stream: nightly.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• openshift/release#77090: Both PRs modify the RHOE certified-operators OCP 4.22 operator-catalog CI YAMLs, adjusting the releases.latest channel configuration.

Suggested labels

lgtm, approved, rehearsals-ack

Suggested reviewers

• hector-vido
• bear-redhat
• bcrochet

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is directly related to the main changeset—updating Red Hat OpenShift Ecosystem (RHOE) 4.22 jobs to use the fast channel, which is the primary change across all modified files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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	PR modifies only YAML CI configuration files, not Go test files. No Ginkgo test names (It/Describe/Context/When) present to validate.
Test Structure And Quality	✅ Passed	PR contains only YAML CI configuration changes; no Ginkgo test code is being modified, making the test quality check not applicable.
Microshift Test Compatibility	✅ Passed	PR adds no new Ginkgo e2e tests—only CI configuration changes to YAML files. The MicroShift check applies only to new test code.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR only modifies CI operator configuration YAML files and does not add any new Ginkgo e2e tests. The check applies only when new tests are added.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies CI operator configuration files only, not deployment manifests, operator code, or controllers. No scheduling constraints are introduced; only release channel configuration changed.
Ote Binary Stdout Contract	✅ Passed	PR contains only YAML CI configuration changes in ci-operator/config/. No Go source code, test binaries, or executable code present; OTE Binary Stdout Contract check not applicable.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	This PR only modifies CI operator YAML configuration files (no new Ginkgo e2e tests added). The custom check only applies when new Ginkgo tests are added, so it is not applicable here.
No-Weak-Crypto	✅ Passed	PR contains only CI/CD configuration YAML files with no cryptographic code, implementations, weak ciphers (MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB), or secret comparison logic.
Container-Privileges	✅ Passed	Modified files are CI configuration files with no container privilege settings: no privileged: true, hostPID/hostNetwork/hostIPC, SYS_ADMIN, or allowPrivilegeEscalation found.
No-Sensitive-Data-In-Logs	✅ Passed	No sensitive data (passwords, tokens, API keys, PII, session IDs, internal hostnames) found in the YAML configuration files. PR only updates release channel settings with no credential logging.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: acornett21

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:

• ci-operator/config/redhat-openshift-ecosystem/certified-operators-preprod/OWNERS [acornett21]
• ci-operator/config/redhat-openshift-ecosystem/certified-operators-prod/OWNERS [acornett21]
• ci-operator/config/redhat-openshift-ecosystem/openshift-preflight/OWNERS [acornett21]
• ci-operator/jobs/redhat-openshift-ecosystem/certified-operators-preprod/OWNERS [acornett21]
• ci-operator/jobs/redhat-openshift-ecosystem/certified-operators-prod/OWNERS [acornett21]
• ci-operator/jobs/redhat-openshift-ecosystem/openshift-preflight/OWNERS [acornett21]

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@acornett21: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-redhat-openshift-ecosystem-openshift-preflight-main-4.22-e2e	redhat-openshift-ecosystem/openshift-preflight	presubmit	Ci-operator config changed
pull-ci-redhat-openshift-ecosystem-openshift-preflight-main-4.22-images	redhat-openshift-ecosystem/openshift-preflight	presubmit	Ci-operator config changed
periodic-ci-redhat-openshift-ecosystem-certified-operators-preprod-ocp-4.22-preflight-preprod-claim	N/A	periodic	Ci-operator config changed
periodic-ci-redhat-openshift-ecosystem-certified-operators-prod-ocp-4.22-preflight-prod-claim	N/A	periodic	Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci]

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