Add coderabbit/ai-slop label to networking repos

[tssurya]

Add the coderabbit/ai-slop label to cluster-network-operator, cloud-network-config-controller, and ovn-kubernetes to flag PRs that may contain AI-generated content needing careful review.

Summary by CodeRabbit

This pull request configures Prow CI to automatically apply the coderabbit/ai-slop label to pull requests in three OpenShift networking component repositories: cluster-network-operator, cloud-network-config-controller, and ovn-kubernetes.

The label serves as a review flag to indicate that a pull request may contain AI-generated content and requires careful human review. This change affects the CI configuration for these specific networking-related components within the OpenShift infrastructure, enabling reviewers to quickly identify and appropriately scrutinize AI-assisted contributions to these critical networking repositories.

[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: 04221fad-d96f-40d5-90c1-08581653ee66

📥 Commits

Reviewing files that changed from the base of the PR and between 980a85f and 2effbef.

📒 Files selected for processing (1)

• core-services/prow/02_config/_labels.yaml

---

Walkthrough

Adds the coderabbit/ai-slop Prow label (color d93f0b, targeting PRs) to three OpenShift repositories — cloud-network-config-controller, cluster-network-operator, and ovn-kubernetes — in the central Prow labels configuration file.

Changes

Prow Label Addition

Layer / File(s)	Summary
coderabbit/ai-slop label entries for three repos core-services/prow/02_config/_labels.yaml	Inserts three repo-specific label blocks defining coderabbit/ai-slop (color d93f0b, target prs, addedBy: label) for openshift/cloud-network-config-controller, openshift/cluster-network-operator, and openshift/ovn-kubernetes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 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 and concisely summarizes the main change: adding a specific label to three networking repositories.
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	PR adds Prow label configuration and standard Go test files, but contains no Ginkgo tests. The check for stable Ginkgo test names is not applicable.
Test Structure And Quality	✅ Passed	The custom check reviews Ginkgo test code quality, but this PR only modifies a YAML configuration file for Prow labels. No test code is present.
Microshift Test Compatibility	✅ Passed	No Ginkgo e2e tests are added in this PR. The changes only modify a Prow label configuration YAML file, making the MicroShift test compatibility check not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR only adds Prow label configuration to _labels.yaml; it contains no new Ginkgo e2e tests, so the SNO compatibility check does not apply.
Topology-Aware Scheduling Compatibility	✅ Passed	PR only modifies Prow CI label configuration file, not deployment manifests, operator code, or controllers. Custom check for topology-aware scheduling is not applicable.
Ote Binary Stdout Contract	✅ Passed	The PR only modifies a Prow YAML configuration file (_labels.yaml) and contains no test binaries, Go code, or OTE-related code that could violate the OTE Binary Stdout Contract.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only adds Prow label configuration in YAML; no Ginkgo e2e tests are added, so the IPv6 compatibility check does not apply.
No-Weak-Crypto	✅ Passed	PR only adds Prow label configuration to YAML file; no cryptographic code, algorithms, or secret comparisons are present.
Container-Privileges	✅ Passed	PR modifies only a Prow label configuration file with no container/K8s manifests; check for container privileges is not applicable.
No-Sensitive-Data-In-Logs	✅ Passed	The PR changes are in a YAML configuration file that defines Prow labels for repositories. The additions contain only metadata (label name, color code, and descriptions) with no logging code or sen...

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

• core-services/prow/02_config/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]

[REHEARSALNOTIFIER]
@tssurya: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

[openshift-ci]

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

[tssurya]

/assign @jmguzik PTAL

[openshift-ci]

@tssurya: GitHub didn't allow me to assign the following users: PTAL.

Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

/assign @jmguzik PTAL

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.