NO-ISSUE: chore(ci): sync quay/quay config (quay#7202)

[quay-devel]

Sync ci-operator config and Prow jobs for quay/quay from ci-generator changes.

• Quay PR: NO-ISSUE: feat(ci): add gcp gcs presubmit alongside the aws s3 one quay/quay#7202
• Quay commit: 1578ad2b4159509fa5fdfe723e67b001bdb3560c
• Workflow run: https://github.com/quay/quay/actions/runs/35100372786
• Push branch: quay-devel/release:sync-quay-ci-config-quay-7202 → openshift/release:main

Summary by CodeRabbit

• Regenerated quay/quay OpenShift CI configuration from ci-generator changes.
• Updated the master configuration to ignore ci-generator/ changes and added an optional GCP test using GCS storage.
• Added a weekly AWS OCP 5.0 installation job for redhat-3.18 with S3, Jaeger, Mailpit, Playwright tests, trace collection, and cleanup.
• No Jira issue is referenced.

[openshift-ci-robot]

@quay-devel: This pull request explicitly references no jira issue.

Details

In response to this:

Sync ci-operator config and Prow jobs for quay/quay from ci-generator changes.

• Quay PR: NO-ISSUE: feat(ci): add gcp gcs presubmit alongside the aws s3 one quay/quay#7202
• Quay commit: 1578ad2b4159509fa5fdfe723e67b001bdb3560c
• Workflow run: https://github.com/quay/quay/actions/runs/35100372786
• Push branch: quay-devel/release:sync-quay-ci-config-quay-7202 → openshift/release:main

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]

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: Advanced

Run ID: 6edb613e-7351-4201-9a62-2a9e8ae3dd7c

📥 Commits

Reviewing files that changed from the base of the PR and between 95bce86 and 58c7a09.

⛔ Files ignored due to path filters (3)

• ci-operator/jobs/quay/quay/quay-quay-master-presubmits.yaml is excluded by !ci-operator/jobs/**
• ci-operator/jobs/quay/quay/quay-quay-redhat-3.18-periodics.yaml is excluded by !ci-operator/jobs/**
• ci-operator/jobs/quay/quay/quay-quay-redhat-3.18-presubmits.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (2)

• ci-operator/config/quay/quay/quay-quay-master.yaml
• ci-operator/config/quay/quay/quay-quay-redhat-3.18__aws-ocp50-e2e-install.yaml

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.

---

Walkthrough

The CI configuration now ignores ci-generator/-only changes, adds optional GCP GCS testing to the master branch, and defines a redhat-3.18 AWS nightly end-to-end test with Quay setup, Playwright execution, tracing, and cleanup.

Changes

Quay CI coverage

Layer / File(s)	Summary
Master CI test configuration ci-operator/config/quay/quay/quay-quay-master.yaml	The skip pattern excludes ci-generator/ paths. An optional gcp-gcs test uses GCP infrastructure, GCS storage, ipi-gcp, and GCP-specific deployment and teardown steps.
Redhat 3.18 AWS nightly test ci-operator/config/quay/quay/quay-quay-redhat-3.18__aws-ocp50-e2e-install.yaml	A new aws-s3-nightly test uses the ipi-aws workflow, provisions Quay dependencies, runs filtered Playwright tests, gathers Jaeger traces, and performs cleanup.

Priority: ⬇️ Low

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Other

Suggested reviewers: jbpratt

Merge Risk: ⚪ Minimal · up to 58c7a

No merge-blocking CI configuration issue was identified.

🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Ipv6 And Disconnected Network Test Compatibility	⚠️ Warning	The pull request adds new Quay E2E CI jobs that require external services. The new aws-ocp50-e2e-install configuration sets PLAYWRIGHT_GIT_REPO to https://github.com/quay/quay.git and `QUAY_INDE…	IPv6 and disconnected network compatibility notice: This test may contain IPv4 assumptions or external connectivity requirements that will fail in IPv6-only disconnected environments. Please verify your test works on IPv6 by running an …

✅ Passed checks (14 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies a CI configuration synchronization for quay/quay and references the related Quay change. It accurately summarizes the main pull request objective.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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 pull request changes only ci-operator YAML configuration and generated Prow job files. The added content contains no Ginkgo title declarations such as It(), Describe(), Context(), or When(), and n…
Test Structure And Quality	✅ Passed	PASS: The pull request changes only five YAML configuration and generated Prow job files. The diff adds CI job definitions and references such as quay-test-e2e, but it adds no Ginkgo test code or `I…
Microshift Test Compatibility	✅ Passed	PASS: The pull request changes only CI YAML and generated Prow job definitions. It adds no Go files, Ginkgo imports, or Ginkgo declarations such as It(), Describe(), Context(), or When(). The referenc…
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PASS: The pull request changes only YAML CI configurations and generated Prow job definitions. The diff adds no Ginkgo test declarations and no test source files. The new jobs invoke the existing `qua…
Topology-Aware Scheduling Compatibility	✅ Passed	The pull request changes only ci-operator test configurations and generated Prow job definitions. It does not add or modify deployment manifests, operator code, or controllers. The added CI definiti…
Ote Binary Stdout Contract	✅ Passed	The pull request changes only five YAML configuration/job files. It adds CI wiring for gcp-gcs, an AWS periodic job, and Playwright image/test execution. The authoritative diff contains no Go or OTE…
No-Weak-Crypto	✅ Passed	PASS: The pull request changes only CI YAML configuration and generated Prow job definitions. The added content contains no MD5, SHA-1, DES, 3DES, RC4, Blowfish, or ECB usage, and it adds no crypto im…
Container-Privileges	✅ Passed	No explicitly disallowed container privilege setting was introduced. The PR additions contain no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, `securityCo…
No-Sensitive-Data-In-Logs	✅ Passed	The pull request adds generated YAML CI configurations and Prow job definitions only. The diff contains no new logging command or log formatter, and it contains no password, token, API key, or credent…

Full details: Ipv6 And Disconnected Network Test Compatibility

Explanation

The pull request adds new Quay E2E CI jobs that require external services. The new aws-ocp50-e2e-install configuration sets PLAYWRIGHT_GIT_REPO to https://github.com/quay/quay.git and QUAY_INDEX_IMAGE_REPO to quay.io/.... Its quay-test-e2e step clones the configured repository. The new gcp-gcs job pulls registry.redhat.io/quay/quay-builder-rhel9. These dependencies are not cluster-internal or mirrored in the changed configuration. No new hardcoded IPv4 assumption was found.

Resolution

IPv6 and disconnected network compatibility notice: This test may contain IPv4 assumptions or external connectivity requirements that will fail in IPv6-only disconnected environments. Please verify your test works on IPv6 by running an additional CI job: For parallel tests: /payload-job periodic-ci-openshift-release-master-nightly-4.22-e2e-metal-ipi-ovn-ipv6 For serial tests (test name contains [Serial]): /payload-job periodic-ci-openshift-release-master-nightly-4.22-e2e-metal-ipi-serial-ovn-ipv6 Use internal mirrors or cluster-local sources for the GitHub repository and public registry images. If the tests cannot run without public internet access, mark the affected test as [Skipped:Disconnected] or apply the equivalent disconnected-environment skip in the CI configuration. In the openshift/origin repo, use GetIPAddressFamily() or GetIPFamilyForCluster() to select IPv6-compatible addresses and CIDRs, or use InIPv4ClusterContext() when a test is IPv4-only.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-ci]

Hi @quay-devel. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: quay-devel
Once this PR has been reviewed and has the lgtm label, please assign hammermeetnail 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/quay/quay/OWNERS
• ci-operator/jobs/quay/quay/OWNERS

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]

@quay-devel: pj-rehearse could not automatically process this event because the request waited in queue for longer than 5 minutes. Use /pj-rehearse to trigger rehearsals manually.