Onboard ocp-perfscale

[rsevilla87]

Summary by CodeRabbit

Onboards openshift-eng/ocp-perfscale to OpenShift CI infrastructure by:

• Adding CI operator configuration to build and promote the repository’s ocp-perfscale image.
• Assigning PerfScale approvers and reviewers.
• Configuring repository-specific Prow plugins, external integrations, approval behavior, and trusted triggers.
• Enabling Tide squash merging with required approval, LGTM, and validation labels.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• ci-operator/jobs/openshift-eng/ocp-perfscale/OWNERS is excluded by !ci-operator/jobs/**

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 77dff9a0-8299-4f7b-933a-8b2ab7643bd4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Walkthrough

Adds repository ownership, CI operator build metadata, Prow plugin settings, trusted triggers, and Tide merge configuration for openshift-eng/ocp-perfscale.

Changes

ocp-perfscale onboarding

Layer / File(s)	Summary
CI build and ownership configuration ci-operator/config/openshift-eng/ocp-perfscale/*	Defines approvers and reviewers, the build-root image, Dockerfile image mapping, image promotion, resource requests, and generated repository metadata.
Prow and Tide repository configuration core-services/prow/02_config/openshift-eng/ocp-perfscale/*	Configures repository ownership, built-in and external plugins, trusted triggers, Tide queries, missing labels, and squash merging.

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

Possibly related PRs

• openshift/release#81734: Adds comparable Prow/Tide onboarding configuration for another repository.
• openshift/release#81862: Adds similar plugin, trigger, and Tide merge configuration for another repository.

🚥 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 matches the main change: onboarding the ocp-perfscale repository into release and Prow configuration.
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	No Ginkgo test titles were added or modified; the PR only changes OWNERS and static CI/prow YAML/job names.
Test Structure And Quality	✅ Passed	Only OWNERS and CI/prow YAML config files were added; no Ginkgo test code or test behavior changed, so the test-quality check is not applicable.
Microshift Test Compatibility	✅ Passed	No Ginkgo/e2e test code was added; the PR only adds OWNERS and ci-operator/prow config, and the new jobs just build/promote images.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR only adds CI/prow config and OWNERS; no Ginkgo e2e tests or SNO-sensitive test logic are introduced.
Topology-Aware Scheduling Compatibility	✅ Passed	Only Prow/ci-operator onboarding config was added; no deployment manifests, controllers, or topology-sensitive scheduling fields were introduced.
Ote Binary Stdout Contract	✅ Passed	Only CI/prow/OWNERS YAML was added; no OTE binary code or process-level stdout writes were introduced.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only adds OWNERS and CI/Prow YAML configs; no new Ginkgo e2e tests or network code were added.
No-Weak-Crypto	✅ Passed	PASS: The changed files are config/OWNERS YAML only, and scans found no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB or custom crypto usage.
Container-Privileges	✅ Passed	The added ci-operator/prow configs and OWNERS files contain no privileged, hostPID/Network/IPC, SYS_ADMIN, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs	✅ Passed	The PR only adds CI/Prow config and job specs; no logging statements or echoed secrets/tokens/PII were introduced.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@rsevilla87: 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-eng-ocp-perfscale-main-images	openshift-eng/ocp-perfscale	presubmit	Presubmit 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.

[openshift-ci]

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

[rsevilla87]

/pj-rehearse ack

[openshift-merge-bot]

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deepsm007, rsevilla87

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:

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

[openshift-ci]

@rsevilla87: Updated the following 2 configmaps:

• config configmap in namespace ci at cluster app.ci using the following files:
  • key core-services-prow-02_config-openshift-eng-ocp-perfscale-_prowconfig.yaml using file core-services/prow/02_config/openshift-eng/ocp-perfscale/_prowconfig.yaml
• config configmap in namespace ci at cluster core-ci using the following files:
  • key core-services-prow-02_config-openshift-eng-ocp-perfscale-_prowconfig.yaml using file core-services/prow/02_config/openshift-eng/ocp-perfscale/_prowconfig.yaml

Details

In response to this:

Summary by CodeRabbit

Onboards openshift-eng/ocp-perfscale to OpenShift CI infrastructure by:

• Adding CI operator configuration to build and promote the repository’s ocp-perfscale image.
• Assigning PerfScale approvers and reviewers.
• Configuring repository-specific Prow plugins, external integrations, approval behavior, and trusted triggers.
• Enabling Tide squash merging with required approval, LGTM, and validation labels.

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.