Skip to content

Conversation

@SergeyKanzhelev
Copy link
Member

As SIG Node manages so many KEPs, we want to keep the high bar for new features, while improving velocity and set clear responsibilities for moving the KEP along towards GA.

This write up formalizes the approach to scaling reviewers and approvers for KEPs in SIG Node in-principle. We will keep working on specifics and potentially automation of creating OWNERS files.

/assign @mrunalp @dchen1107 @derekwaynecarr

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SergeyKanzhelev

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 cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. sig/node Categorizes an issue or PR as relevant to SIG Node. approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jan 26, 2026
@dchen1107
Copy link
Member

+1

Sergey, thanks for the proposal and I am fine with it. Could you please get all sig-node-tech-leads's consensus before merging?

@mrunalp
Copy link
Contributor

mrunalp commented Jan 26, 2026

👍

@derekwaynecarr
Copy link
Member

derekwaynecarr commented Jan 26, 2026 via email

@haircommander
Copy link
Contributor

+1 from me, thanks !

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. sig/node Categorizes an issue or PR as relevant to SIG Node. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants