wg-node-identity: add working group charter and registration by randomvariable · Pull Request #9028 · kubernetes/community

randomvariable · 2026-06-15T23:00:03Z

What this does

Registers a new Working Group: WG Node Identity.

Files changed

sigs.yaml — new WG entry under workinggroups
OWNERS_ALIASES — wg-node-identity-leads alias (chairs to be populated post-approval)
sig-cluster-lifecycle/README.md — generated: WG listed under sponsoring SIG
sig-list.md — generated: WG row added
wg-node-identity/README.md — generated from sigs.yaml
wg-node-identity/charter.md — new charter

Known TODOs (to be resolved before merge)

Slack channel name (#tbd placeholder)
Mailing list URL (not yet created)
Meeting schedule (to be decided by initial WG meeting)
wg-node-identity-leads OWNERS alias populated once chairs confirm

Checklist

sigs.yaml edited directly
Docs regenerated with make generate
Charter follows wg-governance

k8s-ci-robot · 2026-06-15T23:00:08Z

There are empty aliases in OWNER_ALIASES, cleanup is advised.

linux-foundation-easycla · 2026-06-15T23:00:09Z

The committers listed above are authorized under a signed CLA.

✅ login: ahmedtd / name: Taahir Ahmed (e99d345)
✅ login: elmiko / name: Michael McCune (e99d345)
✅ login: hakman / name: Ciprian Hacman (e99d345)
✅ login: pfeifferj / name: Josephine Pfeiffer (e99d345)
✅ login: randomvariable / name: Naadir Jeewa (e99d345)
✅ login: rata / name: Rodrigo Campos Catelin (e99d345)

k8s-ci-robot · 2026-06-15T23:00:11Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: randomvariable
Once this PR has been reviewed and has the lgtm label, please assign cblecker for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

OWNERS

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

randomvariable · 2026-06-15T23:00:24Z

/hold

k8s-ci-robot · 2026-06-15T23:02:10Z

There are empty aliases in OWNER_ALIASES, cleanup is advised.

k8s-ci-robot · 2026-06-15T23:04:18Z

There are empty aliases in OWNER_ALIASES, cleanup is advised.

hakman · 2026-06-29T16:53:44Z

/cc @neolit123

hakman · 2026-06-29T16:53:58Z

/cc @justinsb

neolit123

/approve
in SIGL CL we had consensus this WG to be sponsored.
personally, i mentioned i don't clearly understand what will be product of this WG but let's see.

there could definitely other participating SIGs here, did you get +1 from any others?
has the steering committee +1-ed?

kubernetes-prow · 2026-06-29T17:00:17Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: neolit123, randomvariable
Once this PR has been reviewed and has the lgtm label, please assign cblecker for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

OWNERS

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

neolit123 · 2026-06-30T06:22:50Z

 ## Working Groups

 The following [working groups][working-group-definition] are sponsored by sig-cluster-lifecycle:
+* [WG Node Identity](/wg-node-identity)


sig autoscaling and other sponsors needs to be updated too.
but note they must have agreed to it during a recorded zoom meeting.

the proposal was presented at four SIG meetings:

SIG Autoscaling, 2026-04-23

SIG Node, 2026-04-28

SIG Cluster Lifecycle, 2026-05-12

SIG Auth, 2026-05-20

is sig auth participating?

In some form we need confirmation that the relevant SIGs are in principle +1 and ideally have reviewed teh proposal for any issues they see.

hakman · 2026-07-16T16:05:25Z

/test pull-community-verify

elmiko · 2026-07-16T20:02:00Z

although not a sponsor, i am +1 from the sig cloud provider side.

BenTheElder · 2026-07-21T18:21:22Z

FYI @kubernetes/steering-committee

I think we mainly need evidence of sponsoring SIGs reviewing / agreeing, if you can help collect that then we can move to reviewing the charter in more depth after their feedback. Overall I personally think this looks reasonable at a high level.

jackfrancis · 2026-07-22T19:44:00Z

+1 from SIG Autoscaling

cc @towca @omerap12 @adrianmoisey

elmiko · 2026-07-28T18:43:05Z

@ahmedtd given this comment should we add you to the charter as a chair as well?

ahmedtd · 2026-07-28T19:40:29Z

@ahmedtd given this comment should we add you to the charter as a chair as well?

I would be happy to, but I don't know how many chairs a WG is supposed to have.

BenTheElder · 2026-07-28T20:01:32Z

I would be happy to, but I don't know how many chairs a WG is supposed to have.

There isn't any hard limit, it's recommended to have at least 2, and not recommended to have a LOT, but we have workgroups with as many as 5 chairs currently. 2-4 is typical.

ahmedtd · 2026-07-28T20:05:59Z

I would be happy to, but I don't know how many chairs a WG is supposed to have.

There isn't any hard limit, it's recommended to have at least 2, and not recommended to have a LOT, but we have workgroups with as many as 5 chairs currently. 2-4 is typical.

Then I am fine to just participate.

elmiko · 2026-07-31T13:26:23Z

thanks @ahmedtd , your input is definitely welcome =)

given where we are in the process at this point, i'm curious if sig auth would be willing to give us a +1 towards forming the WG?

elmiko · 2026-07-31T14:01:59Z

cc @aramase @micahhausler @ritazh for a follow up comment on approval from sig auth.

neolit123 · 2026-08-05T20:25:43Z

@randomvariable

please include SIG Auth as participating SIG. this is just a formality. we had the conversation here:
https://kubernetes.slack.com/archives/C0EN96KUY/p1785953599305489

TL;DR

it seems odd to me that a security / authn feature has no expert SIG listed, that should be either Auth or Security. Since @ahmedtd is a SIG Auth regular member, let's include them and he can represent the SIG.
note that if any changes in core k8s like kubelet are required, we need KEPs, and that means core owners. In fact we likely need KEPs for any type of change, unless we align on small docs and blog posts.
sponsoring SIG means a group that wants work done. participating SIG are just advisory. SIG Auth collectively agreed that they do not see the need for work to be done in core ATM.

/hold
until that's resolved.

elmiko · 2026-08-05T20:47:23Z

thanks @neolit123

Registers WG Node Identity across sigs.yaml, OWNERS_ALIASES, sig-list.md, and sig-cluster-lifecycle/README.md, and adds the charter and autogenerated README under wg-node-identity/. Co-authored-by: Taahir Ahmed <taahm@google.com> Co-authored-by: Rodrigo Campos Catelin <rodrigo@sdfg.com.ar> Co-authored-by: Ciprian Hacman <chacman@microsoft.com> Co-authored-by: Naadir Jeewa <naadir.jeewa@broadcom.com> Co-authored-by: Michael McCune <msm@opbstudios.com> Co-authored-by: Josephine Pfeiffer <hi@josie.lol>

randomvariable · 2026-08-06T10:30:36Z

@randomvariable

please include SIG Auth as participating SIG. this is just a formality. we had the conversation here: https://kubernetes.slack.com/archives/C0EN96KUY/p1785953599305489

TL;DR

* it seems odd to me that a security / authn feature has no expert SIG listed, that should be either Auth or Security. Since @ahmedtd is a SIG Auth regular member, let's include them and he can represent the SIG.

* note that if any changes in core k8s like kubelet are required, we need KEPs, and that means core owners. In fact we likely need KEPs for any type of change, unless we align on small docs and blog posts.

* sponsoring SIG means a group that wants work done. participating SIG are just advisory. SIG Auth collectively agreed that they do not see the need for work to be done in core ATM.

/hold until that's resolved.

Thx, we've updated as per conversation.

neolit123 · 2026-08-06T11:39:09Z

+
+* SIG Node
+* SIG Cloud Provider
+* SIG Autoscaling


Suggested change

* SIG Autoscaling

* SIG Autoscaling

* SIG Auth

still missing?

k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Jun 15, 2026

k8s-ci-robot requested review from fabriziopandini and vincepri June 15, 2026 23:00

k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. committee/steering Denotes an issue or PR intended to be handled by the steering committee. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. labels Jun 15, 2026

k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 15, 2026

randomvariable force-pushed the topic/randomvariable/node-identity-wg branch from 526b0cb to 1daa9ab Compare June 15, 2026 23:02

k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Jun 15, 2026

randomvariable force-pushed the topic/randomvariable/node-identity-wg branch from 1daa9ab to cec3d57 Compare June 15, 2026 23:04

randomvariable marked this pull request as draft June 15, 2026 23:05

k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 15, 2026

kubernetes-prow Bot requested a review from neolit123 June 29, 2026 16:53

kubernetes-prow Bot requested a review from justinsb June 29, 2026 16:54

neolit123 reviewed Jun 29, 2026

View reviewed changes

randomvariable force-pushed the topic/randomvariable/node-identity-wg branch from cec3d57 to 616806d Compare June 30, 2026 00:03

randomvariable marked this pull request as ready for review June 30, 2026 00:03

kubernetes-prow Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 30, 2026

neolit123 reviewed Jun 30, 2026

View reviewed changes

kubernetes-prow Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 1, 2026

randomvariable force-pushed the topic/randomvariable/node-identity-wg branch from ef4b3cb to 2feb71c Compare July 31, 2026 20:46

kubernetes-prow Bot added the sig/auth Categorizes an issue or PR as relevant to SIG Auth. label Jul 31, 2026

enj moved this to Needs Triage in SIG Auth Aug 1, 2026

enj added this to SIG Auth Aug 1, 2026

rata reviewed Aug 6, 2026

View reviewed changes

Comment thread wg-node-identity/charter.md

rata force-pushed the topic/randomvariable/node-identity-wg branch from 0b81c2e to 1d49c13 Compare August 6, 2026 10:11

randomvariable force-pushed the topic/randomvariable/node-identity-wg branch 2 times, most recently from e1285ac to f4933cd Compare August 6, 2026 10:21

kubernetes-prow Bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 6, 2026

randomvariable force-pushed the topic/randomvariable/node-identity-wg branch from f4933cd to 9f96bb2 Compare August 6, 2026 10:25

kubernetes-prow Bot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. and removed cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Aug 6, 2026

randomvariable force-pushed the topic/randomvariable/node-identity-wg branch from 9f96bb2 to e99d345 Compare August 6, 2026 10:28

kubernetes-prow Bot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Aug 6, 2026

neolit123 reviewed Aug 6, 2026

View reviewed changes

Uh oh!

Conversation

randomvariable commented Jun 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What this does

Files changed

Known TODOs (to be resolved before merge)

Checklist

Uh oh!

k8s-ci-robot commented Jun 15, 2026

Uh oh!

linux-foundation-easycla Bot commented Jun 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

k8s-ci-robot commented Jun 15, 2026

Uh oh!

randomvariable commented Jun 15, 2026

Uh oh!

k8s-ci-robot commented Jun 15, 2026

Uh oh!

k8s-ci-robot commented Jun 15, 2026

Uh oh!

hakman commented Jun 29, 2026

Uh oh!

hakman commented Jun 29, 2026

Uh oh!

neolit123 left a comment

Choose a reason for hiding this comment

Uh oh!

kubernetes-prow Bot commented Jun 29, 2026

Uh oh!

neolit123 Jun 30, 2026

Choose a reason for hiding this comment

Uh oh!

pfeifferj Jul 5, 2026

Choose a reason for hiding this comment

Uh oh!

neolit123 Jul 5, 2026

Choose a reason for hiding this comment

Uh oh!

BenTheElder Jul 21, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

hakman commented Jul 16, 2026

Uh oh!

elmiko commented Jul 16, 2026

Uh oh!

BenTheElder commented Jul 21, 2026

Uh oh!

jackfrancis commented Jul 22, 2026

Uh oh!

elmiko commented Jul 28, 2026

Uh oh!

ahmedtd commented Jul 28, 2026

Uh oh!

BenTheElder commented Jul 28, 2026

Uh oh!

ahmedtd commented Jul 28, 2026

Uh oh!

elmiko commented Jul 31, 2026

Uh oh!

elmiko commented Jul 31, 2026

Uh oh!

neolit123 commented Aug 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

elmiko commented Aug 5, 2026

Uh oh!

Uh oh!

randomvariable commented Aug 6, 2026

Uh oh!

neolit123 Aug 6, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

randomvariable commented Jun 15, 2026 •

edited

Loading

linux-foundation-easycla Bot commented Jun 15, 2026 •

edited

Loading

neolit123 commented Aug 5, 2026 •

edited

Loading