SPLAT-2637: periodic/e2e/ccm/aws: bump TPNU job to collect data for API promotion

[mtulio]

Bump frequency of the tests for gate to collect data points for promotion.

The tests runs frequently due timeline to gate promotion, as well to have enough data to populate to Sippy with results of tests exposed by OTE by PR openshift/cloud-provider-aws#129 to promote the feature AWSServiceLBNetworkSecurityGroup to GA.

The ticket to rollback the tests to weekly is documented at SPLAT-2666

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[mtulio]

/pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ccm-techpreview

[openshift-ci-robot]

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

[openshift-ci-robot]

[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-release-main-nightly-4.22-e2e-aws-ccm-techpreview	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-robot]

@mtulio: This pull request references SPLAT-2637 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 "4.22.0" version, but no target version was set.

Details

In response to this:

Bump frequency of the tests for gate to collect data points for 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 openshift-eng/jira-lifecycle-plugin repository.

[mtulio]

nightly used by the rehearsal (4.22.0-0.nightly-2026-03-02-153725) still not updated with my changes. Probably I will need to way for healthy nightly builds to proceed.

[jcpowermac]

/lgtm

[openshift-ci-robot]

@mtulio: This pull request references SPLAT-2637 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 "4.22.0" version, but no target version was set.

Details

In response to this:

Bump frequency of the tests for gate to collect data points for promotion.

The tests runs frequently due timeline to gate promotion, as well to have enough data to populate to Sippy with results of tests exposed by OTE by PR openshift/cloud-provider-aws#129 to promote the feature AWSServiceLBNetworkSecurityGroup to GA.

The ticket to rollback the tests to weekly is documented at SPLAT-2666

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.

[mtulio]

nightly used by the rehearsal (4.22.0-0.nightly-2026-03-02-153725) still not updated with my changes. Probably I will need to way for healthy nightly builds to proceed.

The issue is currently under investigation by DPP on Slack: https://redhat-internal.slack.com/archives/CB95J6R4N/p1772568886708639?thread_ts=1772530868.383569&cid=CB95J6R4N

[mtulio]

/pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ccm-techprevie

[openshift-ci-robot]

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

[openshift-ci-robot]

@mtulio: job(s): periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ccm-techprevie either don't exist or were not found to be affected, and cannot be rehearsed

[mtulio]

/pj-rehearse periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-ccm-techpreview

[openshift-ci-robot]

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

[mtulio]

/pj-rehearse ack

[openshift-ci-robot]

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

[wking]

One more fairly standard AWS job each 6h seems like a very small bump to our usual high volume, so I'm fine with this.

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcpowermac, mtulio, wking

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

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.