SPLAT-2588: hypershift: update interval to promote AWSServiceLBNetworkSecurityGroup

[mtulio]

Update e2e-aws-ovn-conformance-techpreview job to get more runs required to promote feature AWSServiceLBNetworkSecurityGroup on API PR openshift/api#2838

This will be reverted to weekly once we have enough runs.

Summary by CodeRabbit

This PR updates the OpenShift HyperShift release 5.0 CI periodic configuration to run the e2e-aws-ovn-conformance-techpreview job more frequently. In ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0__periodics.yaml, the job’s schedule changes from a daily cron (@daily) to an interval: 6h, increasing the number of conformance test runs produced each day.

The intent is to temporarily gather enough test results to support promoting an API change (openshift/api#2838). The change is associated with JIRA SPLAT-2588; the CI robot also flagged that the JIRA ticket may need a configured target version (expected: 5.0.0).

[openshift-ci-robot]

@mtulio: This pull request references SPLAT-2588 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:

Update e2e-aws-ovn-conformance-techpreview job to get more runs required to promote API PR openshift/api#2838

This will be reverted to weekly once we have enough runs.

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

The e2e-aws-ovn-conformance-techpreview periodic job in the HyperShift release-5.0 periodics configuration is updated to replace its cron: '@daily' schedule with interval: 6h, increasing job frequency from once daily to every 6 hours.

Changes

HyperShift Periodic Job Schedule Update

Layer / File(s)	Summary
Job schedule: @daily → 6h interval ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0__periodics.yaml	The e2e-aws-ovn-conformance-techpreview periodic job's scheduling is changed from cron: '@daily' to interval: 6h.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

lgtm, approved, rehearsals-ack

🚥 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	This PR modifies CI job scheduling configuration only (YAML files) and adds documentation. No Ginkgo test definitions or test code files are modified, making this check inapplicable.
Test Structure And Quality	✅ Passed	The custom check reviews Ginkgo test code quality, but this PR only modifies CI job scheduling configuration (YAML), not test code, making the check not applicable.
Microshift Test Compatibility	✅ Passed	PR modifies only job scheduling in a YAML config file, not adding any new Ginkgo e2e tests; check for new tests is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR modifies only CI job scheduling in a YAML configuration file, not new Ginkgo e2e test code. SNO compatibility check only applies when new tests are added.
Topology-Aware Scheduling Compatibility	✅ Passed	This PR modifies a CI/CD job configuration file, not a deployment manifest, operator code, or controller. The change updates a test job's scheduling interval (when it runs), not Kubernetes pod sche...
Ote Binary Stdout Contract	✅ Passed	PR only modifies CI job scheduling YAML configuration, not source code. No code changes exist to violate OTE stdout contract requirements.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	This PR only modifies CI configuration (periodic job scheduling from @daily to 6h interval), not any Ginkgo e2e test code. The check applies only when new tests are added.
No-Weak-Crypto	✅ Passed	PR contains only a CI job scheduling config change from '@daily' to 'interval: 6h' with no cryptographic code, weak crypto algorithms, or secret comparisons.
Container-Privileges	✅ Passed	The modified file is a CI operator configuration (not a K8s manifest) that only changes job scheduling from '@daily' to '6h' interval. No container privilege settings (privileged, hostPID, hostNetw...
No-Sensitive-Data-In-Logs	✅ Passed	No sensitive data exposure detected. PR only changes job scheduling (cron to interval) in a YAML config file. Reporting template and env vars contain no passwords, tokens, API keys, PII, or credent...
Title check	✅ Passed	The title references JIRA issue SPLAT-2588 and mentions updating an interval to promote AWSServiceLBNetworkSecurityGroup, which aligns with the PR objective of increasing test frequency for API promotion.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ 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.}

[mtulio]

/pj-rehearse periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-ovn-conformance-techpreview

[openshift-merge-bot]

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@mtulio: 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
periodic-ci-openshift-hypershift-release-5.0-periodics-e2e-aws-ovn-conformance-techpreview	N/A	periodic	Ci-operator config 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.

[mtulio]

Job is passing.
/pj-rehearse ack

[openshift-merge-bot]

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

[muraee]

/approve

[vr4manta]

/lgtm

[mfbonfigli]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mfbonfigli, mtulio, muraee, vr4manta

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/hypershift/OWNERS [muraee]
• ci-operator/jobs/openshift/hypershift/OWNERS [muraee]

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

[openshift-ci]

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