Skip to content

wg-node-identity: add working group charter and registration#9028

Open
randomvariable wants to merge 1 commit into
kubernetes:mainfrom
randomvariable:topic/randomvariable/node-identity-wg
Open

wg-node-identity: add working group charter and registration#9028
randomvariable wants to merge 1 commit into
kubernetes:mainfrom
randomvariable:topic/randomvariable/node-identity-wg

Conversation

@randomvariable

@randomvariable randomvariable commented Jun 15, 2026

Copy link
Copy Markdown
Member

What this does

Registers a new Working Group: WG Node Identity.

Files changed

  • sigs.yaml — new WG entry under workinggroups
  • OWNERS_ALIASESwg-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

Copy link
Copy Markdown
Contributor

There are empty aliases in OWNER_ALIASES, cleanup is advised.

@linux-foundation-easycla

linux-foundation-easycla Bot commented Jun 15, 2026

Copy link
Copy Markdown

CLA Signed
The committers listed above are authorized under a signed CLA.

  • ✅ login: randomvariable / name: Naadir Jeewa (1daa9ab)

@k8s-ci-robot

Copy link
Copy Markdown
Contributor

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

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 the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Jun 15, 2026
@k8s-ci-robot 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
@randomvariable

Copy link
Copy Markdown
Member Author

/hold

@k8s-ci-robot 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 randomvariable force-pushed the topic/randomvariable/node-identity-wg branch from 526b0cb to 1daa9ab Compare June 15, 2026 23:02
@k8s-ci-robot

Copy link
Copy Markdown
Contributor

There are empty aliases in OWNER_ALIASES, cleanup is advised.

@k8s-ci-robot 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 randomvariable force-pushed the topic/randomvariable/node-identity-wg branch from 1daa9ab to cec3d57 Compare June 15, 2026 23:04
@k8s-ci-robot

Copy link
Copy Markdown
Contributor

There are empty aliases in OWNER_ALIASES, cleanup is advised.

@randomvariable randomvariable marked this pull request as draft June 15, 2026 23:05
@k8s-ci-robot 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
@hakman

hakman commented Jun 29, 2026

Copy link
Copy Markdown
Member

/cc @neolit123

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

hakman commented Jun 29, 2026

Copy link
Copy Markdown
Member

/cc @justinsb

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

@neolit123 neolit123 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

/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

Copy link
Copy Markdown
Contributor

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

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

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/.
@randomvariable randomvariable force-pushed the topic/randomvariable/node-identity-wg branch from cec3d57 to 616806d Compare June 30, 2026 00:03
@randomvariable randomvariable marked this pull request as ready for review June 30, 2026 00:03
@kubernetes-prow 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
@kubernetes-prow

Copy link
Copy Markdown
Contributor

@randomvariable: 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
pull-community-verify 616806d link true /test pull-community-verify

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

## Working Groups

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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

is sig auth participating?

- Developing any node attestation mechanism outside of the ownership of a sponsoring SIG.
- Long term ownership of cloud provider-specific implementations of attestation verifiers
- Workload identity (existing solutions exist)
- Removal of bootstrap token support — bootstrap tokens will remain available as a fallback, but attestation should be the default for distributions that support it

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

unlikely for the kubeadm team to agree on that.
the regular k8s user doesn't care about atestation.

@kubernetes-prow

Copy link
Copy Markdown
Contributor

PR needs rebase.

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.

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

@pfeifferj pfeifferj left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

added some small comments to clarify

Comment thread sigs.yaml
Comment on lines +3850 to +3852
stakeholder_sigs:
- Autoscaling
- Cluster Lifecycle

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

iirc only SIG Cluster Lifecycle gave a sponsoring +1 (in the 2026-05-12 meeting). SIG Node said they're time-constrained to sponsor and would participate instead (2026-04-28), and as I understood autoscaling is an interested consumer rather than a sponsor.

since the generated SIG READMEs render every stakeholder_sigs entry as "sponsored by", this should probably be:

Suggested change
stakeholder_sigs:
- Autoscaling
- Cluster Lifecycle
stakeholder_sigs:
- Cluster Lifecycle

* SIG Cluster Lifecycle
* SIG Autoscaling
* SIG Cloud Provider

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
## Stakeholders
Sponsoring SIGs:
* SIG Cluster Lifecycle
Participating SIGs:
* SIG Node
* SIG Cloud Provider
* SIG Autoscaling

### Progress Reporting

- Annual reports to the steering committee (due by 1 March)
- Quarterly updates to sponsoring SIG mailing lists (sig-node@, sig-cluster-lifecycle@, @sig-cloud-provider)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
- Quarterly updates to sponsoring SIG mailing lists (sig-node@, sig-cluster-lifecycle@, @sig-cloud-provider)
- Quarterly updates to sponsoring and participating SIG mailing lists (sig-cluster-lifecycle@, sig-node@, sig-cloud-provider@, sig-autoscaling@)

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

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. committee/steering Denotes an issue or PR intended to be handled by the steering committee. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. 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.

5 participants