CORENET-7235: Update OWNERS file

[raphaelvrosa]

Summary by CodeRabbit

• Chores
  • Updated the project’s ownership configuration by refreshing reviewer and approver assignments.
  • Removed outdated entries and added new reviewers and approvers while keeping key existing contacts.
  • Left the Networking component ownership entry unchanged.

[openshift-ci-robot]

@raphaelvrosa: This pull request references CORENET-7235 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: 415cb161-3625-4a03-be25-6c38e8db57e6

📥 Commits

Reviewing files that changed from the base of the PR and between e1d564f and e6c1189.

📒 Files selected for processing (1)

• OWNERS

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

• OWNERS

---

Walkthrough

This PR updates OWNERS reviewer and approver assignments for the Networking component by removing prior entries, retaining selected owners, and adding new assignments.

Changes

OWNERS assignments

Layer / File(s)	Summary
Reviewer and approver list updates OWNERS	Reviewer and approver lists are updated to remove prior usernames, retain selected owners, and add additional assignments.

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

Suggested reviewers: s1061123, zeeke

🚥 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: 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 only changes OWNERS; no test titles or Ginkgo specs were modified, so the naming check is not implicated.
Test Structure And Quality	✅ Passed	PR only changes OWNERS; no Ginkgo test files or test logic were modified, so the test-quality check is not applicable.
Microshift Test Compatibility	✅ Passed	PR changes only OWNERS; no test files or Ginkgo specs were added, so MicroShift compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Only OWNERS changed; no Ginkgo e2e tests were added or modified, so SNO compatibility is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	PR only updates OWNERS; no deployment manifests, controllers, or scheduling constraints were changed.
Ote Binary Stdout Contract	✅ Passed	Only OWNERS changed; no process-level code or stdout writes were added, so the OTE stdout contract is unaffected.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Only OWNERS changed; no new Ginkgo e2e tests or networking code, so this compatibility check is not applicable.
No-Weak-Crypto	✅ Passed	Only OWNERS changed; diff updates reviewer/approver lists and contains no crypto code or weak-crypto patterns.
Container-Privileges	✅ Passed	PR only changes OWNERS; no container/K8s manifests were modified, so no new privileged settings were introduced.
No-Sensitive-Data-In-Logs	✅ Passed	PR only changes OWNERS reviewer/approver lists; no code, logs, or sensitive data were added.

✨ 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/images	e6c1189	link	true	/test images

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.