CORENET-7234: Update OWNERS file

[raphaelvrosa]

Summary by CodeRabbit

• Chores
  • Updated the project’s code review and approval configuration by revising the set of reviewers and approvers for the relevant component.

[openshift-ci-robot]

@raphaelvrosa: This pull request references CORENET-7234 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 "5.0.0" version, but no target version was set.

Details

In response to this:

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]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: dc415e50-e8df-4c2f-9f5c-3ce7ea302fc7

📥 Commits

Reviewing files that changed from the base of the PR and between 25baaab and 7b69ff4.

📒 Files selected for processing (1)

• OWNERS

🚧 Files skipped from review as they are similar to previous changes (1)

• OWNERS

---

Walkthrough

The OWNERS file updates reviewer and approver membership for the multus component. The reviewer roster is replaced, and the approver roster is narrowed while adding wizhaoredhat. Component metadata remains unchanged.

Changes

OWNERS membership update

Layer / File(s)	Summary
Reviewer and approver roster updates OWNERS	The reviewers list removes several names and establishes a new roster. The approvers list is narrowed to seven entries and adds wizhaoredhat; component metadata remains unchanged.

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

Suggested reviewers: aneeshkp, jeremyeder

🚥 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 accurately summarizes the main change: updating the OWNERS file.
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 changes only OWNERS; no test files or Ginkgo titles were modified.
Test Structure And Quality	✅ Passed	Only OWNERS changed; no Ginkgo test code was added or modified, so the test-structure check is not applicable.
Microshift Test Compatibility	✅ Passed	PR changes only OWNERS; no Ginkgo tests or new APIs/features were added, so MicroShift compatibility is not impacted.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Only OWNERS changed; no new Ginkgo tests or SNO-relevant code were added, so the check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	Only OWNERS metadata changed; no deployment manifests, operators, or controllers were modified, so no topology-aware scheduling risk is introduced.
Ote Binary Stdout Contract	✅ Passed	PR only changes OWNERS; no process-level code or stdout writes were touched.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Only OWNERS changed; no Ginkgo/e2e tests were added or modified, so IPv4/disconnected-network compatibility isn’t applicable.
No-Weak-Crypto	✅ Passed	PR only changes OWNERS; no crypto code, weak algorithms, custom crypto, or secret comparisons were introduced.
Container-Privileges	✅ Passed	PR only changes OWNERS; no container/K8s manifests or privilege-related fields appear in the diff.
No-Sensitive-Data-In-Logs	✅ Passed	Only OWNERS changed; no code or log statements were added, so no sensitive data logging risk is introduced.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[bpickard22]

/lgtm

[bpickard22]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bpickard22, raphaelvrosa

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:

• OWNERS [bpickard22]

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bpickard22, raphaelvrosa

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:

• OWNERS [bpickard22]

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

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci]

@raphaelvrosa: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/security	7b69ff4	link	false	/test security

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.