Update 4.18 automated-release jobs to use sustaining cloud accounts

[MrSanketkumar]

Updates the cluster profiles of 4.18 automated-release jobs to use sustaining cloud accounts

Summary by CodeRabbit

The PR updates OpenShift 4.18 automated-release and stage-testing jobs to use sustaining cloud accounts. It replaces QE autorelease cluster profiles and base domains with sustaining equivalents for AWS, Azure, and GCP upgrade and release test configurations.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: MrSanketkumar
Once this PR has been reviewed and has the lgtm label, please assign rrasouli 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:

• ci-operator/config/openshift/openshift-tests-private/OWNERS
• ci-operator/jobs/openshift/openshift-tests-private/OWNERS

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

[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: 0c2351a9-405b-4879-b7e0-1101c87d35c4

📥 Commits

Reviewing files that changed from the base of the PR and between 7886e6e and 8675152.

⛔ Files ignored due to path filters (1)

• ci-operator/jobs/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.18-periodics.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (4)

• ci-operator/config/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.18__automated-release-stable-4.18-upgrade-from-stable-4.17.yaml
• ci-operator/config/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.18__automated-release-stable-4.18-upgrade-from-stable-4.18.yaml
• ci-operator/config/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.18__automated-release.yaml
• ci-operator/config/openshift/openshift-tests-private/openshift-openshift-tests-private-release-4.18__stage-testing.yaml

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

Walkthrough

The change updates release, upgrade, and stage-testing configurations to use sustaining autorelease cluster profiles and corresponding sustaining base domains.

Changes

Sustaining autorelease configuration

Layer / File(s)	Summary
Update test environment targets ci-operator/config/openshift/openshift-tests-private/*release-4.18*.yaml, ci-operator/config/openshift/openshift-tests-private/*stage-testing.yaml	AWS, Azure, and GCP test jobs now use sustaining autorelease cluster profiles. AWS and Azure jobs also use sustaining base domains where configured.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to 86751

This localized configuration update switches 4.18 automated-release jobs to sustaining cloud profiles; no actionable merge-blocking risk remains beyond completing the standard configuration regeneration and validation checks.

🚥 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 clearly summarizes the migration of 4.18 automated-release jobs to sustaining cloud accounts.
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	The commit changes only YAML cluster profiles, domains, and generated job labels; no Ginkgo It, Describe, Context, or When test titles were added or modified.
Test Structure And Quality	✅ Passed	The PR changes only five YAML CI configuration/generated job files and introduces no Ginkgo test code or test constructs, so this check is inapplicable.
Microshift Test Compatibility	✅ Passed	The PR changes only YAML cluster profiles, domains, and generated job labels; the diff adds no Ginkgo tests or test source changes to assess for MicroShift compatibility.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The diff changes only YAML CI configurations and generated Prow job labels; it adds no Ginkgo tests or test code, so SNO compatibility rules do not apply.
Topology-Aware Scheduling Compatibility	✅ Passed	The commit changes only CI YAML cluster_profile, BASE_DOMAIN, and generated cloud-cluster-profile values; it adds no deployment manifests, operator code, controllers, or scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The complete PR diff changes only five YAML job/config files; it adds no OTE source or process-level stdout/logging writes.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The diff changes only YAML cluster profiles, base domains, and generated job labels; it adds no Ginkgo tests or IPv4/external-connectivity code.
No-Weak-Crypto	✅ Passed	The complete diff changes only YAML cluster-profile, base-domain, and generated label values; it adds no MD5, SHA1, DES, RC4, Blowfish, ECB, crypto code, or secret comparisons.
Container-Privileges	✅ Passed	The patch changes only cluster_profile, BASE_DOMAIN, and generated labels; no changed file adds privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, root, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs	✅ Passed	The diff adds only cluster-profile labels and BASE_DOMAIN configuration; the additions contain no logging statements, credentials, tokens, PII, or log output.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@MrSanketkumar: 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-openshift-tests-private-release-4.18-automated-release-stable-4.18-upgrade-from-stable-4.18-gcp-ipi-f999	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.18-automated-release-aws-ipi-disruptive-f999	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.18-automated-release-azure-upi-f999	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.18-automated-release-stable-4.18-upgrade-from-stable-4.17-azure-ipi-fips-f999	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.18-automated-release-stable-4.18-upgrade-from-stable-4.17-azure-upi-f999	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.18-automated-release-aws-ipi-f999	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.18-automated-release-stable-4.18-upgrade-from-stable-4.18-azure-ipi-fips-f999	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.18-automated-release-stable-4.18-upgrade-from-stable-4.17-gcp-ipi-f999	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.18-stage-testing-e2e-aws-ipi	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.18-automated-release-stable-4.18-upgrade-from-stable-4.18-azure-upi-f999	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.18-automated-release-gcp-ipi-f999	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.18-automated-release-stable-4.18-upgrade-from-stable-4.18-aws-ipi-f999	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.18-automated-release-stable-4.18-upgrade-from-stable-4.17-aws-ipi-f999	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-openshift-tests-private-release-4.18-automated-release-azure-ipi-fips-f999	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]

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

[tomasdavidorg]

@MrSanketkumar The cluster profiles have been changed for azure, see #80553

[tomasdavidorg]

Suggested change

	cluster_profile: azure-sustaining-autorelease-412
	cluster_profile: openshift-org-azure

[tomasdavidorg]

Suggested change

	cluster_profile: azure-sustaining-autorelease-412
	cluster_profile: openshift-org-azure

[tomasdavidorg]

Suggested change

	cluster_profile: azure-sustaining-autorelease-412
	cluster_profile: openshift-org-azure

[tomasdavidorg]

Suggested change

	cluster_profile: azure-sustaining-autorelease-412
	cluster_profile: openshift-org-azure

[tomasdavidorg]

Suggested change

	cluster_profile: azure-sustaining-autorelease-412
	cluster_profile: openshift-org-azure

[tomasdavidorg]

Suggested change

	BASE_DOMAIN: sustaining-az-412.azure.devcluster.openshift.com
	BASE_DOMAIN: ci.azure.devcluster.openshift.com

[tomasdavidorg]

Suggested change

	BASE_DOMAIN: sustaining-az-412.azure.devcluster.openshift.com
	BASE_DOMAIN: ci.azure.devcluster.openshift.com

[tomasdavidorg]

Suggested change

	BASE_DOMAIN: sustaining-az-412.azure.devcluster.openshift.com
	BASE_DOMAIN: ci.azure.devcluster.openshift.com

[tomasdavidorg]

Suggested change

	BASE_DOMAIN: sustaining-az-412.azure.devcluster.openshift.com
	BASE_DOMAIN: ci.azure.devcluster.openshift.com

[tomasdavidorg]

Suggested change

	BASE_DOMAIN: sustaining-az-412.azure.devcluster.openshift.com
	BASE_DOMAIN: ci.azure.devcluster.openshift.com