wg-node-identity: add working group charter and registration#9028
wg-node-identity: add working group charter and registration#9028randomvariable wants to merge 1 commit into
Conversation
|
There are empty aliases in OWNER_ALIASES, cleanup is advised. |
|
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: randomvariable The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/hold |
526b0cb to
1daa9ab
Compare
|
There are empty aliases in OWNER_ALIASES, cleanup is advised. |
1daa9ab to
cec3d57
Compare
|
There are empty aliases in OWNER_ALIASES, cleanup is advised. |
|
/cc @neolit123 |
|
/cc @justinsb |
neolit123
left a comment
There was a problem hiding this comment.
/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?
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: neolit123, randomvariable The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
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/.
cec3d57 to
616806d
Compare
|
@randomvariable: The following test failed, say
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. DetailsInstructions 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) |
There was a problem hiding this comment.
sig autoscaling and other sponsors needs to be updated too.
but note they must have agreed to it during a recorded zoom meeting.
There was a problem hiding this comment.
the proposal was presented at four SIG meetings:
| - 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 |
There was a problem hiding this comment.
unlikely for the kubeadm team to agree on that.
the regular k8s user doesn't care about atestation.
|
PR needs rebase. DetailsInstructions 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. |
pfeifferj
left a comment
There was a problem hiding this comment.
added some small comments to clarify
| stakeholder_sigs: | ||
| - Autoscaling | ||
| - Cluster Lifecycle |
There was a problem hiding this comment.
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:
| stakeholder_sigs: | |
| - Autoscaling | |
| - Cluster Lifecycle | |
| stakeholder_sigs: | |
| - Cluster Lifecycle |
| * SIG Cluster Lifecycle | ||
| * SIG Autoscaling | ||
| * SIG Cloud Provider | ||
|
|
There was a problem hiding this comment.
| ## 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) |
There was a problem hiding this comment.
| - 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@) |
What this does
Registers a new Working Group: WG Node Identity.
Files changed
sigs.yaml— new WG entry underworkinggroupsOWNERS_ALIASES—wg-node-identity-leadsalias (chairs to be populated post-approval)sig-cluster-lifecycle/README.md— generated: WG listed under sponsoring SIGsig-list.md— generated: WG row addedwg-node-identity/README.md— generated fromsigs.yamlwg-node-identity/charter.md— new charterKnown TODOs (to be resolved before merge)
#tbdplaceholder)wg-node-identity-leadsOWNERS alias populated once chairs confirmChecklist
sigs.yamledited directlymake generate