SIG Architecture

[Brian Grant]

At the leadership summit a few weeks ago, I believe there was consensus that we should start an Architecture SIG. There were also discussions of Working Groups around extensibility and repo refactoring, but I'd like to fold that into SIG Architecture, since they are all related, and because I've been driving these areas, directly or indirectly, and there are only so many meetings I can attend.

This is the proposal for such a SIG, as the first step in the SIG creation procedure:

https://github.com/kubernetes/community/blob/master/sig-governance.md#sig-creation-procecure

Initial mission statement (thanks to Jaice):

The SIG would be intended to guide the design principles of Kubernetes, as well as provide a consistent body of expertise necessary to ensure architectural consistency over time.

The scope would cover the whole project -- issues that span/encompass all the components, how they fit together, how they interact, etc. But the SIG would not get involved with issues specific to a particular component or functional area, which would be the purview of some other SIG, except where they deviate from project-wide principles/conventions.

The specific areas I propose are:

Defining the scope of the Kubernetes project:

• https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/
  
• Ecosystem examples

Documenting and evolving the system architecture:

• https://github.com/kubernetes/community/blob/master/contributors/design-proposals/architecture.md
  
• Kubernetes Architecture presentation
• Kubernetes Architectural roadmap working document

Defining and driving necessary extensibility points.

Establishing and documenting design principles and conventions for the overall system and user-facing APIs:

• https://github.com/kubernetes/community/blob/master/contributors/design-proposals/principles.md
  
• https://github.com/kubernetes/community/blob/master/contributors/devel/api-conventions.md
  Note that the API conventions aren't part of API machinery because that SIG is about the mechanisms for building the apiservers, APIs, and client libraries, not the principles/conventions driving the design of the APIs and their contents.

Driving improvement of overall code organization -- multiple repos, etc.

Developing necessary review processes, such as the proposal and API review processes.

Educating approvers/owners of other SIGs (e.g., by holding office hours).

Suggested meeting day/time: Thursday @ 9am Pacific, before the community meeting, biweekly

[Ihor Dvoretskyi]

Big +1 from me. It's long-awaited and we definitely need a place to discuss architecture questions and make architecture decisions.

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CAKCBhs6Wmq%2BKgo8ayrnHvS-jL-MBFgv%3DoUj%2BpS7-u_jFdM-QHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Clayton Coleman]

+1 - there have been several sig discussions recently about having a more streamlined way to seek consensus on broad reaching technical changes, and this seems like a natural (possibly overdue) sig.

[Andy Goldstein]

+1 from me too

On Thu, Jun 22, 2017 at 4:37 PM, Clayton Coleman <ccol...@redhat.com> wrote:

+1 - there have been several sig discussions recently about having a more streamlined way to seek consensus on broad reaching technical changes, and this seems like a natural (possibly overdue) sig.

To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CAKCBhs6Wmq%2BKgo8ayrnHvS-jL-MBFgv%3DoUj%2BpS7-u_jFdM-QHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/-737520277828820344%40unknownmsgid.

[Eric Tune]

+1.

+1 from me too

To post to this group, send email to kuberne...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CAKCBhs6Wmq%2BKgo8ayrnHvS-jL-MBFgv%3DoUj%2BpS7-u_jFdM-QHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.

To post to this group, send email to kuberne...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/-737520277828820344%40unknownmsgid.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CANtdwzbc_WOWNaj44c3SH-%3DmBL_jX8sZdrWe5r7sfc3_j51xAA%40mail.gmail.com.

[Vishnu Kannan]

+1

+1.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CANtdwzbc_WOWNaj44c3SH-%3DmBL_jX8sZdrWe5r7sfc3_j51xAA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CAASt_VEGNSCMgDMQUH6OczfCmhopMA09xrRoVjsP8wTezJLwBQ%40mail.gmail.com.

[Dawn Chen]

+1. 

+1.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CANtdwzbc_WOWNaj44c3SH-%3DmBL_jX8sZdrWe5r7sfc3_j51xAA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CAASt_VEGNSCMgDMQUH6OczfCmhopMA09xrRoVjsP8wTezJLwBQ%40mail.gmail.com.

[Joseph Jacks]

+1.

[Michael Hausenblas]

+1

[pmo...@redhat.com]

+1 to this - I have wanted this to be a thing at many times while working on service-catalog.

[feisky]

+1.

在 2017年6月23日星期五 UTC+8上午4:12:48，Brian Grant写道：

[Joris van der Kwast]

+1

Op donderdag 22 juni 2017 22:12:48 UTC+2 schreef Brian Grant:

[Michail Kargakis]

+1

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.

[Jamie Hannaford]

+1

Can we emphasise in the mission statement that the SIG is concerned with the architecture of the Kubernetes project and codebase(s)? Before I read it I assumed it was about how to architect apps on Kubernetes. I'm sure other folks might make that assumption too.

[DL duglin]

Overall, big +1

> But the SIG would not get involved with issues specific to a particular component or functional area, which would be the purview of some other SIG, except where they deviate from project-wide principles/conventions.

I'd like some discussion around this as SIG-Arch is established. While I definitely do not want SIG-Arch to micro-manage other SIGs, how will they know if a SIG is making a decision that "deviates from the project-wide principles" if the decision/discussions are all local to that SIG? I'm wondering if new features should be passed along to SIG-Arch not for review but as an FYI. Then its up to the members of SIG-Arch to ask more questions if they have concerns/questions.

-Doug

On Thursday, June 22, 2017 at 4:12:48 PM UTC-4, Brian Grant wrote:

[Brian Grant]

On Fri, Jun 23, 2017 at 5:36 AM, DL duglin <dug...@gmail.com> wrote:

Overall, big +1

> But the SIG would not get involved with issues specific to a particular component or functional area, which would be the purview of some other SIG, except where they deviate from project-wide principles/conventions.

I'd like some discussion around this as SIG-Arch is established. While I definitely do not want SIG-Arch to micro-manage other SIGs, how will they know if a SIG is making a decision that "deviates from the project-wide principles" if the decision/discussions are all local to that SIG? I'm wondering if new features should be passed along to SIG-Arch not for review but as an FYI. Then its up to the members of SIG-Arch to ask more questions if they have concerns/questions.

Review processes and escalations.

A fair number of these come to individuals (e.g., me) today. 

I also attend SIG PM for the feature-review meetings, and asked all the SIGs to create the numerous teams and mailing lists to try to winnow down the info overload to enable proposals to be visible.

 

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/51e42c49-954e-4497-83fb-bd1c6c72364c%40googlegroups.com.

[William Denniss]

+1.

I think it makes sense to have a home for the architectural direction of Kubernetes.

To post to this group, send email to kuberne...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/51e42c49-954e-4497-83fb-bd1c6c72364c%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CAKCBhs71h%2B0i-yc96-DkjHQDP1pHggvcb0%2BqhEfK5esJeQTarw%40mail.gmail.com.

[Brendan Burns]

Where does this stand? Have we established a mailing list or an initial meeting date?

[Brian Grant]

Jaice has been helping with the logistics. 

Mailing lists have been created.

First meeting is 7/10 @ 10am Pacific.

Hopefully info will be added to the community repo soon.

On Thu, Jun 29, 2017 at 8:51 AM, Brendan Burns <brendan...@gmail.com> wrote:

Where does this stand? Have we established a mailing list or an initial meeting date?

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/b3bcfffc-7bcf-4939-9c9a-d4d2e8b04724%40googlegroups.com.

[Tim St. Clair]

I have not seen a PR with the logistics update to:
https://github.com/kubernetes/community/blob/master/sig-list.md



On Thu, Jun 29, 2017 at 11:35 AM, 'Brian Grant' via Kubernetes
developer/contributor discussion <kuberne...@googlegroups.com>
wrote:

> Jaice has been helping with the logistics.
>
> Mailing lists have been created.
>
> First meeting is 7/10 @ 10am Pacific.
>
> Hopefully info will be added to the community repo soon.
>
> On Thu, Jun 29, 2017 at 8:51 AM, Brendan Burns <brendan...@gmail.com>
> wrote:
>>
>> Where does this stand? Have we established a mailing list or an initial
>> meeting date?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Kubernetes developer/contributor discussion" group.
>> To unsubscribe from this group and stop receiving emails from it, send an

>> email to kubernetes-de...@googlegroups.com.
>> To post to this group, send email to kuberne...@googlegroups.com.

>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/kubernetes-dev/b3bcfffc-7bcf-4939-9c9a-d4d2e8b04724%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>

> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes developer/contributor discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to kubernetes-de...@googlegroups.com.
> To post to this group, send email to kuberne...@googlegroups.com.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/kubernetes-dev/CAKCBhs46-TuWJFYRJ6h3SoWyrszGR--_-iULAJhPArvP2cFmiA%40mail.gmail.com.

>
> For more options, visit https://groups.google.com/d/optout.

--
Cheers,
Timothy St. Clair

“Do all the good you can. By all the means you can. In all the ways
you can. In all the places you can. At all the times you can. To all
the people you can. As long as ever you can.”

[Quinton Hoole]

LGTM

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CAKCBhs6Wmq%2BKgo8ayrnHvS-jL-MBFgv%3DoUj%2BpS7-u_jFdM-QHQ%40mail.gmail.com.

[Brian Grant]

Jaice said he had a problem with the SIG doc generator and was working on that.

On Wed, Jul 5, 2017 at 7:41 AM, Tim St. Clair <timo...@gmail.com> wrote:

I have not seen a PR with the logistics update to:
https://github.com/kubernetes/community/blob/master/sig-list.md



On Thu, Jun 29, 2017 at 11:35 AM, 'Brian Grant' via Kubernetes

developer/contributor discussion <kubernetes-dev@googlegroups.com>
wrote:

> Jaice has been helping with the logistics.
>
> Mailing lists have been created.
>
> First meeting is 7/10 @ 10am Pacific.
>
> Hopefully info will be added to the community repo soon.
>
> On Thu, Jun 29, 2017 at 8:51 AM, Brendan Burns <brendan...@gmail.com>
> wrote:
>>
>> Where does this stand? Have we established a mailing list or an initial
>> meeting date?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Kubernetes developer/contributor discussion" group.
>> To unsubscribe from this group and stop receiving emails from it, send an

>> email to kubernetes-dev+unsubscribe@googlegroups.com.
>> To post to this group, send email to kubernetes-dev@googlegroups.com.

>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/kubernetes-dev/b3bcfffc-7bcf-4939-9c9a-d4d2e8b04724%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes developer/contributor discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to kubernetes-dev+unsubscribe@googlegroups.com.
> To post to this group, send email to kubernetes-dev@googlegroups.com.

> To view this discussion on the web visit

[Jaice Singer DuMars]

Sorry for the delay.  The generator was not working properly on my system so I had to reset my env.  There's a PR up now, ready for review/merge:

https://github.com/kubernetes/community/pull/784

Last step is creating the GitHub teams, which I anticipate will be done today.

On Wednesday, July 5, 2017 at 11:37:43 AM UTC-4, Brian Grant wrote:

Jaice said he had a problem with the SIG doc generator and was working on that.

On Wed, Jul 5, 2017 at 7:41 AM, Tim St. Clair <timo...@gmail.com> wrote:

I have not seen a PR with the logistics update to:
https://github.com/kubernetes/community/blob/master/sig-list.md



On Thu, Jun 29, 2017 at 11:35 AM, 'Brian Grant' via Kubernetes

developer/contributor discussion <kuberne...@googlegroups.com>
wrote:

> Jaice has been helping with the logistics.
>
> Mailing lists have been created.
>
> First meeting is 7/10 @ 10am Pacific.
>
> Hopefully info will be added to the community repo soon.
>
> On Thu, Jun 29, 2017 at 8:51 AM, Brendan Burns <brendan...@gmail.com>
> wrote:
>>
>> Where does this stand? Have we established a mailing list or an initial
>> meeting date?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Kubernetes developer/contributor discussion" group.
>> To unsubscribe from this group and stop receiving emails from it, send an

>> email to kubernetes-de...@googlegroups.com.
>> To post to this group, send email to kuberne...@googlegroups.com.

>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/kubernetes-dev/b3bcfffc-7bcf-4939-9c9a-d4d2e8b04724%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Kubernetes developer/contributor discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to kubernetes-de...@googlegroups.com.
> To post to this group, send email to kuberne...@googlegroups.com.

> To view this discussion on the web visit