Proposal: change WG K8s Infra to SIG K8s Infra

Aaron Crickenberger

unread,

Jul 30, 2021, 1:10:10 PM7/30/21

to steering

Hi Steering!

I come to you, fully formed proposal in hand, to ask for your consensus on changing WG K8s Infra into a SIG. I wanted to start the conversation here before going straight to opening PRs. If there is sufficient support, we can get started on that for formal approval on a kubernetes/community PR.

- aaron

Benjamin Elder

unread,

Jul 30, 2021, 1:30:30 PM7/30/21

to Aaron Crickenberger, steering

Was this discussed with any of the SIGs mentioned? Or in the WG?

Can comment access be opened on the doc?

Is there a reason this is going only to steering and not kubernetes-dev?

--
You received this message because you are subscribed to the Google Groups "steering" group.
To unsubscribe from this group and stop receiving emails from it, send an email to steering+u...@kubernetes.io.
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/84e4c562-c49f-417d-a772-e73558ab07d6n%40kubernetes.io.

Aaron Crickenberger

unread,

Jul 30, 2021, 2:24:51 PM7/30/21

to steering, Benjamin Elder, steering, Aaron Crickenberger

>Was this discussed with any of the SIGs mentioned? Or in the WG?

I discussed this privately with stakeholder SIG leads and the WG leads. The intent was to gain some kind of consensus before opening up for broader review. This e-mail is that call for broader review: the decision has not been made, merely recommended for further consideration.

Mea culpa, I only realized after pressing send that I did not seek formal approval from each stakeholder SIG prior to sending this out. Nor did I pass this around to all of kubernetes-dev prior to sending this out. I planned on raising this within the WG if seemed like Steering was in favor, and calling for kubernetes-dev review and approval from stakeholder SIGs formally via PR and lazy consensus

If Steering would prefer I instead shop this through all of the aforementioned venues, I am happy to do so.

> Can comment access be opened on the doc?

I fixed up permissions shortly after sending out, my bad.

> Is there a reason this is going only to steering and not kubernetes-dev?

See above.

- aaron

Benjamin Elder

unread,

Jul 30, 2021, 3:26:31 PM7/30/21

to Aaron Crickenberger, steering

Thanks Aaron.

Reply all

Reply to author

Forward