CORENET-7235: Update OWNERS file

[raphaelvrosa]

Summary by CodeRabbit

• Chores
  • Updated internal code review and approval assignments.

[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]

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: 3ecfb032-462e-4919-bb09-35697f7715bb

📥 Commits

Reviewing files that changed from the base of the PR and between 43b1645 and 2c24cb7.

📒 Files selected for processing (1)

• OWNERS

---

Walkthrough

This PR updates the OWNERS file to reassign reviewers and approvers for the Networking component. The reviewers list is modified to add new members while keeping fepan, bpickard22, and zeeke. The approvers list is adjusted to include LionelJouin, danwinship, and SchSeba while retaining fepan and bpickard22.

Changes

OWNERS File Updates

Layer / File(s)	Summary
Reviewer and approver assignments OWNERS	Reviewers list adds new members and retains fepan, bpickard22, and zeeke. Approvers list adds LionelJouin, danwinship, and SchSeba while retaining fepan and bpickard22.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Test Structure And Quality	⚠️ Warning	Ginkgo tests lack meaningful failure messages in assertions. Assertions like Expect(err).NotTo(HaveOccurred()) and Expect(result).To(BeFalse()) provide no diagnostic context when failures occur.	Add failure message context to assertions, e.g., Expect(err).NotTo(HaveOccurred(), "failed to create test pod") throughout all test files to aid diagnosis of test failures.

✅ 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 accurately describes the main change: updating the OWNERS file with new reviewer and approver assignments.
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	All Ginkgo test names are stable and deterministic. No dynamic values like generated pod names, timestamps, UUIDs, node names, or IP addresses found in test titles.
Microshift Test Compatibility	✅ Passed	No new Ginkgo e2e tests are added in this PR. The PR only updates the OWNERS file (reviewer/approver assignments), with no test code changes or additions.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR only updates the OWNERS file with reviewer/approver assignments. No new Ginkgo e2e tests are being added. The check does not apply to non-test file changes.
Topology-Aware Scheduling Compatibility	✅ Passed	PR only modifies OWNERS file (code review metadata), not deployment manifests, operator code, or controllers that could introduce topology-unaware scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	Code complies with OTE Binary Stdout Contract: main.go uses ctrl.SetLogger(zap.New(...)) with no direct stdout writes, and suite_test.go uses GinkgoWriter for test logging.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only updates OWNERS file metadata; no new Ginkgo e2e tests are added. Check is not applicable.
No-Weak-Crypto	✅ Passed	PR only modifies OWNERS configuration file with GitHub usernames. No cryptographic code, weak crypto patterns, or insecure comparisons present.
Container-Privileges	✅ Passed	PR only modifies OWNERS file (repository access config), not container/K8s manifests. Custom check for container privileges is not applicable.
No-Sensitive-Data-In-Logs	✅ Passed	PR only modifies OWNERS file with GitHub usernames; no logging statements or sensitive data (passwords, tokens, keys, PII) are present.

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

[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]

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