Automated - Update config ./config/openshift.yaml

[openshift-bot]

No description provided.

[openshift-ci-robot]

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: automatic mode

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-bot
Once this PR has been reviewed and has the lgtm label, please assign deepsm007 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[coderabbitai]

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

💤 Files selected but had no reviewable changes (2)

• config/openshift.yaml
• pkg/variantregistry/snapshot.yaml

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 90e5daa9-f85b-46e3-93ed-2037142e3779

📥 Commits

Reviewing files that changed from the base of the PR and between 289a9bc and bf01615.

📒 Files selected for processing (2)

• config/openshift.yaml
• pkg/variantregistry/snapshot.yaml

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

Walkthrough

Updated OpenShift CI configuration files to rename release variant identifiers from -f7 to -f14 across multiple platforms and topologies, and added new variant entries for AWS HPA jobs (releases 4.21–4.23), an agent OVN single-node job (release 4.22), and GCP verification test variants.

Changes

Cohort / File(s)

Summary

OpenShift CI Release Configuration & Variant Registry config/openshift.yaml, pkg/variantregistry/snapshot.yaml

Systematic renaming of release variant identifier suffixes from -f7 to -f14 across AWS, GCP, Azure, vSphere, Nutanix, and Baremetal platforms. Added new periodic e2e AWS HPA job variants for Kubernetes releases 4.21, 4.22, and 4.23; added agent OVN single-node job variant for release 4.22; added GCP ipi verification test variants with -f14 suffix for releases 4.21–5.0. Regenerated CI release configuration metadata with updated timestamps.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Go Error Handling	✅ Passed	The pull request modifies only YAML configuration files without any Go source code changes, making the Go error handling check not applicable.
Sql Injection Prevention	✅ Passed	SQL Injection Prevention check is not applicable to this PR. Modified files are YAML configuration files with CI/CD pipeline definitions and variant registry configurations. No SQL queries or dynamic SQL construction found.
Excessive Css In React Should Use Styles	✅ Passed	PR modifies only YAML configuration files with no React components, JSX code, or CSS styling.
Single Responsibility And Clear Naming	✅ Passed	PR modifies only YAML configuration files with no changes to code-level packages, structs, methods, or naming conventions.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-ci]

@openshift-bot: The following test 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/lint	bf01615	link	true	/test lint

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.