Update OWNERS file

[pcbailey]

Update owners file to remove old entries and add team members.

Summary by CodeRabbit

• Chores
  • Updated team membership and reviewer assignments for the Networking component's repository metadata.

Note: This change only updates ownership/review metadata and does not affect end-user functionality or product features.

[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: 08122fbc-294d-4b9b-83ea-4122df91c474

📥 Commits

Reviewing files that changed from the base of the PR and between 7e7f98f and 8be782f.

📒 Files selected for processing (1)

• OWNERS

✅ Files skipped from review due to trivial changes (1)

• OWNERS

---

Walkthrough

The OWNERS file updates the Networking component members: the approvers list is replaced with a new set of usernames, and the reviewers list is modified (added adamviktora, removed tnisan, yaacov, hstastna, and reordered remaining entries).

Changes

Team membership update

Layer / File(s)	Summary
Approvers and reviewers roster updates OWNERS	Approvers list updated (added/removed/reordered usernames); reviewers list updated (added adamviktora, removed tnisan, yaacov, hstastna, and reordered remaining reviewers).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 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 'Update OWNERS file' is directly related to the changeset, which only modifies the OWNERS file with updated approvers and reviewers lists.
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	This PR updates only the OWNERS metadata file and contains no Ginkgo tests. The repository is a TypeScript/JavaScript project using Cypress and Jest, not Go/Ginkgo. The check is not applicable.
Test Structure And Quality	✅ Passed	This PR only updates the OWNERS metadata file with no test code changes. The custom check for Ginkgo test structure and quality is not applicable.
Microshift Test Compatibility	✅ Passed	This PR updates only the OWNERS file and adds configuration/documentation files. No new Ginkgo e2e tests (Go test files) are added, making the MicroShift test compatibility check inapplicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR only updates OWNERS metadata file; does not add any Ginkgo e2e tests, so SNO test compatibility check does not apply.
Topology-Aware Scheduling Compatibility	✅ Passed	PR only modifies OWNERS metadata file; does not add or modify deployment manifests, operator code, or scheduling constraints. Check is not applicable to repository metadata changes.
Ote Binary Stdout Contract	✅ Passed	PR only modifies OWNERS metadata file with no code changes, so no stdout contract violations possible in process-level code.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only updates OWNERS file; no Ginkgo e2e tests are added. Custom check for IPv6 and disconnected network compatibility applies only to new Ginkgo tests, not applicable here.
No-Weak-Crypto	✅ Passed	PR updates OWNERS metadata only; no cryptographic code or weak algorithms present in changes.
Container-Privileges	✅ Passed	PR contains no privileged container settings: containers run as non-root (USER 1001), no privileged/hostPID/hostNetwork/hostIPC flags, no SYS_ADMIN capability, no allowPrivilegeEscalation setting.
No-Sensitive-Data-In-Logs	✅ Passed	The PR only modifies OWNERS file and adds repository files with no logging statements exposing passwords, tokens, APIs, PII, or other sensitive data.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ 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 and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

OWNERS (1)

1-2: ⚠️ Potential issue | 🟠 Major

Don’t directly edit auto-generated OWNERS; update the ci-tools generation source instead
OWNERS is explicitly marked DO NOT EDIT; this file is auto-generated using https://github.com/openshift/ci-tools. and contains the approvers/reviewers lists—so changing those lists by committing edits to this file can be overwritten on the next generation run and bypass the intended ownership/audit workflow. Update the underlying ci-tools/owners source data that generates this OWNERS file per the OpenShift ci-docs process (instead of editing the generated file).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@OWNERS` around lines 1 - 2, The OWNERS file is auto-generated and must not be
edited directly; instead update the ci-tools source that generates it (the
OpenShift ci-tools owners config) so approvers/reviewers changes persist. Locate
the ci-tools owners data used to produce OWNERS (the repository/config used by
the generator referenced in the header) and make your edits there, then re-run
the generation pipeline so OWNERS is regenerated with your updated
approvers/reviewers.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@OWNERS`:
- Around line 1-2: The OWNERS file is auto-generated and must not be edited
directly; instead update the ci-tools source that generates it (the OpenShift
ci-tools owners config) so approvers/reviewers changes persist. Locate the
ci-tools owners data used to produce OWNERS (the repository/config used by the
generator referenced in the header) and make your edits there, then re-run the
generation pipeline so OWNERS is regenerated with your updated
approvers/reviewers.

---

ℹ️ Review info

⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: f13d2fa1-ffe0-43a8-a06e-4ba3cd2d2be4

📥 Commits

Reviewing files that changed from the base of the PR and between 0e0f374 and 7e7f98f.

📒 Files selected for processing (1)

• OWNERS

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: avivtur, pcbailey

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 [avivtur,pcbailey]

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]

@pcbailey: 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/e2e-tests	8be782f	link	true	/test e2e-tests

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.

[pcbailey]

/verify-owners

[openshift-ci]

The OWNERS file contains untrusted users, which makes it INVALID. The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the openshift org. You can then trigger verification by writing /verify-owners in a comment.

• parthivk100
  • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.