Skip to content

Add distinct owners files to reflect the shared ownership of the repo#2997

Open
swetharepakula wants to merge 2 commits intokubernetes:masterfrom
swetharepakula:add-owners
Open

Add distinct owners files to reflect the shared ownership of the repo#2997
swetharepakula wants to merge 2 commits intokubernetes:masterfrom
swetharepakula:add-owners

Conversation

@swetharepakula
Copy link
Member

  • L4, NEG, PSC are owned by one team
  • L7 is owned by one team

/assign @kl52752
/assign @mmamczur

/hold Do not merge until both assignees LGTM

@k8s-ci-robot k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Oct 6, 2025
@k8s-ci-robot k8s-ci-robot requested review from aojea and sawsa307 October 6, 2025 18:33
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: swetharepakula

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:

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

@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Oct 6, 2025
@swetharepakula swetharepakula force-pushed the add-owners branch 2 times, most recently from 79cf228 to 41a3f48 Compare October 9, 2025 00:00
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 15, 2025
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 27, 2026
@swetharepakula
Copy link
Member Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 12, 2026
@k8s-ci-robot k8s-ci-robot added do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Feb 12, 2026
The following folks are no longer working on ingress-gce:
  * mrhohn
  * panslava
  * cezarygerard
  * code-elinka
  * gauravkghildiyal
  * sawsa307
@swetharepakula swetharepakula force-pushed the add-owners branch 2 times, most recently from 3cf29a4 to f16f8b2 Compare February 12, 2026 02:14
 * L4, NEG, PSC are owned by one team
 * L7 is owned by one team
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Feb 12, 2026
@@ -1,3 +1,5 @@
options:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this intended to have so limited approvers? with no parent owners it will mean we can't do changes here without bothering Bowei or Tim

@@ -0,0 +1,10 @@
options:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually removed L4 completely from this package. unless I missed something but should be mostly L4 free

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you could actually add ownership of pkg/l4resources and pkg/l4config to the L4 team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants