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 |
cec3d57 to
616806d
Compare
| ## 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:
There was a problem hiding this comment.
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.
Thx, we've updated as per conversation. |
|
|
||
| * SIG Node | ||
| * SIG Cloud Provider | ||
| * SIG Autoscaling |
There was a problem hiding this comment.
| * SIG Autoscaling | |
| * SIG Autoscaling | |
| * SIG Auth |
still missing?
|
/cc |
|
@alicefr: GitHub didn't allow me to request PR reviews from the following users: alicefr. Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this:
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. |
|
just leaving a note, we are planning to discuss this topic at the sig cluster-lifecycle meeting next week. in specific we are going to discuss if we need a working group, or if we might continue towards a KEP as a subproject of cluster-lifecycle. |
| Sponsoring SIGs: | ||
|
|
||
| * SIG Cluster Lifecycle | ||
|
|
||
| Participating SIGs: | ||
|
|
||
| * SIG Node | ||
| * SIG Cloud Provider | ||
| * SIG Autoscaling |
There was a problem hiding this comment.
we met again today in the SIG CL meeting and discussed this list:
| Sponsoring SIGs: | |
| * SIG Cluster Lifecycle | |
| Participating SIGs: | |
| * SIG Node | |
| * SIG Cloud Provider | |
| * SIG Autoscaling | |
| Sponsoring SIGs: | |
| * SIG Autoscaling | |
| * SIG Cloud Provider | |
| * SIG Cluster Lifecycle | |
| Participating SIGs: | |
| * SIG Auth | |
| * SIG Node | |
There was a problem hiding this comment.
updated to set stakeholders.
|
/sig node autoscaling cloud-provider |
e99d345 to
fe70f29
Compare
|
updated to set the stakeholders as discussed. since we are adding sig cloud provider to sponsors i'd like to ping @bridgetkromhout @JoelSpeed and @cheftako |
neolit123
left a comment
There was a problem hiding this comment.
/lgtm
/cc @BenTheElder
please ping the steering slack if needed.
|
/hold cancel |
fe70f29 to
7388e37
Compare
|
updated other references to reflect the stakeholders. |
7388e37 to
e32cc14
Compare
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>
e32cc14 to
f76fbdb
Compare
|
ok, think i got all the references updated =) |
|
[This is on @kubernetes/steering-committee agenda] |
|
@BenTheElder are working groups discussed in the public meeting or will that be for the steering-only meeting? |
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