ROSAENG-61894: Add hypershift-ci sector nightly periodic jobs

[dustman9000]

Summary

• Adds ci-operator config variant hypershift-ci for HyperShift operator validation nightly periodics
• Integration: two jobs targeting hypershift-dev sector (4.22 stable, 5.0 nightly)
• Staging: two jobs targeting hypershift-ci sector (4.22 stable, 5.0 nightly)
• Uses CLUSTER_SECTOR to route HCP provisioning to dedicated MC/SC in us-west-2

Context

Dedicated sectors for HyperShift operator CI are now available in both environments. These nightly jobs validate HO health against real ROSA infrastructure, providing the foundation for future presubmit testing on openshift/hypershift PRs.

Part of ROSAENG-61876 (HyperShift Operator Coverage).

Test plan

• pj-rehearse passes for all four new periodic jobs
• After merge, verify first nightly runs provision HCPs on their respective sectors
• Confirm Sippy picks up results under the new job names

Summary by CodeRabbit

• Introduces a new hypershift-ci variant for the ROSA HCP e2e CI-operator configuration (ci-operator/config/openshift-online/rosa-e2e/openshift-online-rosa-e2e-main__hypershift-ci.yaml), intended for the dedicated staging sector.
• Sets up the hypershift-ci build/root images and defaults (including required base images in the ci namespace and build_root image tag), along with baseline resource requests/limits for jobs.
• Adds four nightly/stable cron-scheduled HCP e2e periodic jobs using workflow rosa-e2e-hcp and profile rosa-e2e-01:
  • Stable (OCP 4.22) runs at 0 5 * * * (integration) and 0 6 * * * (staging)
  • Nightly (OCP 5.0) runs at 30 5 * * * (integration) and 30 6 * * * (staging)
• Ensures provisioning is routed to the dedicated us-west-2 management/service clusters by setting CLUSTER_SECTOR: hypershift-ci (staging) and includes consistent hypershift-ci environment wiring (e.g., HOSTED_CP: true, ENABLE_BILLING_ACCOUNT: yes, LABEL_FILTER: Platform:HCP, REPLICAS: 3) with run-to-run differences in OCM_LOGIN_ENV, CHANNEL_GROUP (stable vs nightly), and OPENSHIFT_VERSION (4.22 vs 5.0).

[openshift-ci-robot]

@dustman9000: This pull request references ROSAENG-61894 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 "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

• Adds ci-operator config variant hypershift-ci for the dedicated hypershift-ci sector in staging
• Creates two nightly HCP e2e periodics targeting the hypershift-ci sector: 4.22 stable and 5.0 nightly
• Uses CLUSTER_SECTOR: hypershift-ci to route HCP provisioning to the dedicated MC/SC in us-west-2

Context

The hypershift-ci sector (MC: hs-mc-c73desao0, SC: hs-sc-c73deqtb0) is now available in staging. These nightly jobs validate HyperShift operator health against real ROSA infrastructure on a dedicated sector, providing the foundation for future presubmit testing on openshift/hypershift PRs.

Part of ROSAENG-61876 (HyperShift Operator Coverage).

Test plan

• pj-rehearse passes for both new periodic jobs
• After merge, verify first nightly run provisions HCP on hypershift-ci sector successfully
• Confirm Sippy picks up results under the new job names

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.

[coderabbitai]

Walkthrough

Adds a ROSA hypershift CI configuration with build images, an rosa-e2e output image, OCP release settings, default resources, four scheduled ROSA HCP E2E workflows, and generated metadata.

Changes

ROSA HCP CI

Layer / File(s)	Summary
Build, release, and resource configuration ci-operator/config/openshift-online/rosa-e2e/...yaml	Adds required base images, the rosa-e2e build output, an OCP 4.22 nightly release candidate, and default job resource settings.
Scheduled ROSA HCP E2E workflows ci-operator/config/openshift-online/rosa-e2e/...yaml	Adds four cron-scheduled integration and staging workflows for stable 4.22 and nightly 5.0, with environment-specific settings and generated repository metadata.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: ravitri, gdbranco

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
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 only adds ci-operator YAML/job config; no Ginkgo test titles or dynamic strings were introduced in changed files.
Test Structure And Quality	✅ Passed	PR only adds generated ci-operator YAML; no Go/Ginkgo test code changed, so the test-structure check is not applicable.
Microshift Test Compatibility	✅ Passed	PR only adds ci-operator YAML/job defs; no new Ginkgo test code or unsupported OpenShift API usage was introduced.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR only adds ci-operator/job YAML; no new Ginkgo test code or test bodies were introduced, so SNO compatibility is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	Only ci-operator/job YAML was added; no deployment manifests, controllers, or scheduling constraints were modified.
Ote Binary Stdout Contract	✅ Passed	PR only changes ci-operator YAML/job metadata; no main/TestMain/suite code or stdout writes were added.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No new Ginkgo tests or IPv4-specific logic were added; this PR only wires existing rosa-e2e-hcp jobs.
No-Weak-Crypto	✅ Passed	The changed YAML only defines CI jobs and resources; it contains no weak crypto, custom crypto, or secret/token comparisons.
Container-Privileges	✅ Passed	New ci-operator/job YAML adds no privileged, hostPID/Network/IPC, SYS_ADMIN, root, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs	✅ Passed	No new logging/echo code or sensitive values were added; the PR only adds ci-operator YAML and standard secret mounts/env vars.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: adding hypershift-ci periodic jobs for the ROSA E2E config.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dustman9000

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/openshift-online/rosa-e2e/OWNERS [dustman9000]
• ci-operator/jobs/openshift-online/rosa-e2e/OWNERS [dustman9000]

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]
@dustman9000: 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-openshift-online-rosa-e2e-main-hypershift-ci-images	openshift-online/rosa-e2e	presubmit	Presubmit changed
periodic-ci-openshift-online-rosa-e2e-main-hypershift-ci-rosa-hcp-e2e-integration-nightly-5-0	N/A	periodic	Periodic changed
periodic-ci-openshift-online-rosa-e2e-main-hypershift-ci-rosa-hcp-e2e-integration-stable-4-22	N/A	periodic	Periodic changed
periodic-ci-openshift-online-rosa-e2e-main-hypershift-ci-rosa-hcp-e2e-staging-stable-4-22	N/A	periodic	Periodic changed
periodic-ci-openshift-online-rosa-e2e-main-hypershift-ci-rosa-hcp-e2e-staging-nightly-5-0	N/A	periodic	Periodic changed

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.

[dustman9000]

/pj-rehearse periodic-ci-openshift-online-rosa-e2e-main-hypershift-ci-rosa-hcp-e2e-integration-stable-4-22 periodic-ci-openshift-online-rosa-e2e-main-hypershift-ci-rosa-hcp-e2e-staging-stable-4-22

[openshift-merge-bot]

@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci]

@dustman9000: 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/rehearse/periodic-ci-openshift-online-rosa-e2e-main-hypershift-ci-rosa-hcp-e2e-integration-stable-4-22	bf01e0d	link	unknown	/pj-rehearse periodic-ci-openshift-online-rosa-e2e-main-hypershift-ci-rosa-hcp-e2e-integration-stable-4-22

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.