Merge pull request #2830 from spiffxp/wg-k8s-infra
Add wg-k8s-infra with draft charter
This commit is contained in:
Kubernetes Prow Robot
GitHub
commit
6d7d04d06e
|
|
@ -132,6 +132,9 @@ aliases:
|
|||
- dejanb
|
||||
- ptone
|
||||
- cantbewong
|
||||
wg-k8s-infra-leads:
|
||||
- dims
|
||||
- spiffxp
|
||||
wg-kubeadm-adoption-leads:
|
||||
- luxas
|
||||
- justinsb
|
||||
|
|
|
|||
|
|
@ -63,6 +63,7 @@ When the need arises, a [new SIG can be created](sig-creation-procedure.md)
|
|||
|[Component Standard](wg-component-standard/README.md)|* [Lucas Käldström](https://github.com/luxas), Luxas Labs (occasionally contracting for Weaveworks)<br>* [Dr. Stefan Schimanski](https://github.com/sttts), Red Hat<br>* [Michael Taufen](https://github.com/mtaufen), Google<br>|* [Slack](https://kubernetes.slack.com/messages/)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-component-standard)|* Regular WG Meeting: [Tuesdays at 08:30 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/18TsodX0fqQgViQ7HHUTAhiAwkf6bNhPXH4vNVTI7GwI)<br>
|
||||
|[Container Identity](wg-container-identity/README.md)|* [Clayton Coleman](https://github.com/smarterclayton), Red Hat<br>* [Greg Castle](https://github.com/destijl), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-container-identity)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-container-identity)|* Regular WG Meeting: [Wednesdays at 10:00 PDT (bi-weekly (On demand))](https://zoom.us/my/k8s.sig.auth)<br>
|
||||
|[IoT Edge](wg-iot-edge/README.md)|* [Cindy Xing](https://github.com/cindyxing), Huawei<br>* [Dejan Bosanac](https://github.com/dejanb), Red Hat<br>* [Preston Holmes](https://github.com/ptone), Google<br>* [Steve Wong](https://github.com/cantbewong), VMWare<br>|* [Slack](https://kubernetes.slack.com/messages/wg-iot-edge)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-iot-edge)|* Regular WG Meeting: [Fridays at 16:00 UTC (bi-weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|
||||
|[K8s Infra](wg-k8s-infra/README.md)|* [Davanum Srinivas](https://github.com/dims), Huawei<br>* [Aaron Crickenberger](https://github.com/spiffxp), Google<br>|* [Slack](https://kubernetes.slack.com/messages/k8s-infra-team)<br>* [Mailing List](https://groups.google.com/forum/#!forum/k8s-infra-team)|* Regular WG Meeting: [Wednesdays at 8:30 PT (Pacific Time) (bi-weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|
||||
|[Kubeadm Adoption](wg-kubeadm-adoption/README.md)|* [Lucas Käldström](https://github.com/luxas), Luxas Labs (occasionally contracting for Weaveworks)<br>* [Justin Santa Barbara](https://github.com/justinsb)<br>|* [Slack](https://kubernetes.slack.com/messages/sig-cluster-lifecycle)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle)|* Regular WG Meeting: [Tuesdays at 18:00 UTC (bi-weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|
||||
|[Machine Learning](wg-machine-learning/README.md)|* [Vishnu Kannan](https://github.com/vishh), Google<br>* [Kenneth Owens](https://github.com/kow3ns), Google<br>* [Balaji Subramaniam](https://github.com/balajismaniam), Intel<br>* [Connor Doyle](https://github.com/ConnorDoyle), Intel<br>|* [Slack](https://kubernetes.slack.com/messages/wg-machine-learning)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-machine-learning)|* Regular WG Meeting: [Thursdays at 13:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|
||||
|[Multitenancy](wg-multitenancy/README.md)|* [David Oppenheimer](https://github.com/davidopp), Google<br>* [Jessie Frazelle](https://github.com/jessfraz), Microsoft<br>|* [Slack](https://kubernetes.slack.com/messages/wg-multitenancy)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-multitenancy)|* Regular WG Meeting: [Wednesdays at 11:00 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
|
||||
|
|
|
|||
28
sigs.yaml
28
sigs.yaml
|
|
@ -2413,4 +2413,30 @@ workinggroups:
|
|||
url: https://docs.google.com/document/d/18TsodX0fqQgViQ7HHUTAhiAwkf6bNhPXH4vNVTI7GwI
|
||||
contact:
|
||||
mailing_list: https://groups.google.com/forum/#!forum/kubernetes-wg-component-standard
|
||||
|
||||
- name: K8s Infra
|
||||
dir: wg-k8s-infra
|
||||
mission_statement: >
|
||||
A Working Group dedicated to migrating Kubernetes project infrastructure
|
||||
over to the CNCF, and the creation of teams and processes for ongoing
|
||||
maintenance. Involves collaboration with multiple SIGs such as
|
||||
Architecture, Contributor Experience, Release, and Testing, etc.
|
||||
charter_link: charter.md
|
||||
leadership:
|
||||
chairs:
|
||||
- name: Davanum Srinivas
|
||||
github: dims
|
||||
company: Huawei
|
||||
- name: Aaron Crickenberger
|
||||
github: spiffxp
|
||||
company: Google
|
||||
meetings:
|
||||
- description: Regular WG Meeting
|
||||
day: Wednesday
|
||||
time: "8:30"
|
||||
tz: "PT (Pacific Time)"
|
||||
frequency: bi-weekly
|
||||
url: https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit
|
||||
archive_url: http://bit.ly/wg-k8s-infra-notes
|
||||
contact:
|
||||
slack: k8s-infra-team # TODO(spiffxp): rename to wg-k8s-infra
|
||||
mailing_list: https://groups.google.com/forum/#!forum/k8s-infra-team # TODO(spiffxp): rename to wg-k8s-infra
|
||||
|
|
|
|||
|
|
@ -0,0 +1,30 @@
|
|||
<!---
|
||||
This is an autogenerated file!
|
||||
|
||||
Please do not edit this file directly, but instead make changes to the
|
||||
sigs.yaml file in the project root.
|
||||
|
||||
To understand how this file is generated, see https://git.k8s.io/community/generator/README.md
|
||||
--->
|
||||
# K8s Infra Working Group
|
||||
|
||||
A Working Group dedicated to migrating Kubernetes project infrastructure over to the CNCF, and the creation of teams and processes for ongoing maintenance. Involves collaboration with multiple SIGs such as Architecture, Contributor Experience, Release, and Testing, etc.
|
||||
|
||||
The [charter](charter.md) defines the scope and governance of the K8s Infra Working Group.
|
||||
|
||||
## Meetings
|
||||
* Regular WG Meeting: [Wednesdays at 8:30 PT (Pacific Time)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit) (bi-weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=8:30&tz=PT%20%28Pacific%20Time%29).
|
||||
* [Meeting notes and Agenda](http://bit.ly/wg-k8s-infra-notes).
|
||||
|
||||
## Organizers
|
||||
|
||||
* Davanum Srinivas (**[@dims](https://github.com/dims)**), Huawei
|
||||
* Aaron Crickenberger (**[@spiffxp](https://github.com/spiffxp)**), Google
|
||||
|
||||
## Contact
|
||||
* [Slack](https://kubernetes.slack.com/messages/k8s-infra-team)
|
||||
* [Mailing list](https://groups.google.com/forum/#!forum/k8s-infra-team)
|
||||
|
||||
<!-- BEGIN CUSTOM CONTENT -->
|
||||
|
||||
<!-- END CUSTOM CONTENT -->
|
||||
|
|
@ -0,0 +1,131 @@
|
|||
# WG K8s Infra Charter
|
||||
|
||||
This charter adheres to the [wg-governance] guidance, as well as
|
||||
adheres to the general conventions described in the [Kubernetes
|
||||
Charter README] and the Roles and Organization Management outlined
|
||||
in [sig-governance], where applicable to a Working Group.
|
||||
|
||||
## Scope
|
||||
|
||||
The K8s Infra Working Group is interested in the successful migration of all
|
||||
project infrastructure from Google (or elsewhere) to the CNCF, such that the
|
||||
project is able to sustainably operate itself without direct assistance from
|
||||
entities such as Google or Red Hat.
|
||||
|
||||
### Disband criteria
|
||||
|
||||
It is our intent to disband once this migration is complete, with ownership
|
||||
of all code, processes and teams assigned to the appropriate SIGs. If we find
|
||||
that this is not possible, we will work with the Steering Committee and
|
||||
respective SIGs to find a more sustainable model (SIG, Committee or Team)
|
||||
|
||||
### In scope
|
||||
|
||||
#### Code, Binaries and Services
|
||||
|
||||
External facing services implemented as subprojects. They often span multiple
|
||||
SIGs in terms of ownership, hence why this WG is acting as a steward of their
|
||||
migration.
|
||||
|
||||
| Service | SIG(s) | Notes |
|
||||
| --- | --- | --- |
|
||||
| DNS | Contribex, Release | Domain Name Services for Kubernetes assets |
|
||||
| GAE | Testing | Gubernator, Testgerid |
|
||||
| GCB | Release | Used to build releases |
|
||||
| GCR | Release | Repository for Container Images |
|
||||
| GCS / Object Storage | Release, Testing | Buckets for logs, test artifacts, release tarballs, APT, RPM |
|
||||
| GKE + Stack Driver | Contribex, Release, Testing | Clusters for running bots, utilities, prow, etc |
|
||||
| Big Query | Testing | Data for test results |
|
||||
| Website / Blogs | Contribex, CNCF | Communications platform |
|
||||
| Pool of compute resources for testing | Testing, CNCF, Cloud Providers| GCE, AWS |
|
||||
|
||||
Internal infrastructure which will be necessary to support these, including:
|
||||
|
||||
- Credential store to work across teams
|
||||
- Certificate store for signing certs
|
||||
- Github repo for storing artifacts like scripts/yamls
|
||||
- and for requesting resources (using github issues as tickets?)
|
||||
|
||||
Documented policies and processes for how to staff and structure these
|
||||
subprojects, including:
|
||||
|
||||
- naming schemes
|
||||
- teams and ACL's
|
||||
- vetting criteria
|
||||
- on-call / escalation policies
|
||||
|
||||
#### Cross-cutting and Externally Facing Processes
|
||||
|
||||
##### Deploying Changes
|
||||
|
||||
We aspire to remain agile and deploy quickly, while ensuring a disruption-free
|
||||
experience for project contributors. As such, the amount of notice we provide
|
||||
and the amount of consensus we seek is driven by our estimation of risk. We
|
||||
don't currently define risk in terms of objective metrics, so here is a rough
|
||||
description of the guidelines we follow. We anticipate refining these over
|
||||
time.
|
||||
|
||||
- **Low risk** changes do not break existing contributor workflows, are easy
|
||||
to roll back, and impact at most a few project repos or SIGs. These should
|
||||
be reviewed by another member of WG K8s infra or the affected SIG(s),
|
||||
preferably an approver.
|
||||
|
||||
- **Medium risk** changes may impact existing contributor workflows, should be
|
||||
easy to roll back, and may impact all of the project's repos. These should
|
||||
be shared with the appropriate SIGs, and may require a [lazy consensus]
|
||||
issue with [kubernetes-dev@] notice.
|
||||
|
||||
- **High risk changes** likely break existing contributor workflows, may be
|
||||
difficult to roll back, and likely impact all of the project's repos. These
|
||||
require a consultation with SIG Contributor Experience as well as any other
|
||||
owning SIGs, and a [lazy consensus] issue with [kubernetes-dev@] notice.
|
||||
|
||||
### Out of Scope
|
||||
|
||||
- We are not responsible for maintaining infrastructure which has not yet been
|
||||
migrated to the CNCF. For example, problems with prow.k8s.io should be routed
|
||||
to SIG Testing.
|
||||
|
||||
## Roles and Organization Management
|
||||
|
||||
- Proposing and making decisions _MAY_ be done without the use of KEPS so long
|
||||
as the decision is documented in a linkable medium. We prefer to see written
|
||||
decisions and reasoning on the [wg-k8s-infra@] mailing list or as issues
|
||||
filed against [kubernetes/k8s.io]. We encourage the use of faster mediums
|
||||
such as slack of video conferences to come to consensus.
|
||||
|
||||
- It is our intent that each infra-related subproject identified for migration
|
||||
must be staffed / owned by at least 3 volunteers
|
||||
|
||||
- We aspire to follow the same 1/3 maximal representation rules used by the
|
||||
Steering Committee, Product Security Team, and other groups that have
|
||||
project-wide impact
|
||||
- However, while we are bootstrapping, we consider it acceptable for maximal
|
||||
representation concerns to be violated, since this will often be necessary
|
||||
for Google-staffed subprojects to divest themselves of the infrastructure.
|
||||
- Our plan would be to rectify this when choosing new members or rotating
|
||||
old members such that we eventually meet maximal representation criteria
|
||||
|
||||
- We plan to follow the model set forth by the Product Security Team for
|
||||
suitable vetting new subproject owners
|
||||
|
||||
- Subproject owners must provide additional contact details within the WG, and
|
||||
we will need to identify when and how it is appropriate to share these with
|
||||
other parts of the project. Such details include:
|
||||
- Alternate e-mails
|
||||
- Phone numbers
|
||||
- Timezone
|
||||
|
||||
- As this is a Working Group, we own no code and cannot create subprojects. We
|
||||
will instead identify and petition the appropriate SIG for subproject
|
||||
creation. We will provide guidelines on how the relevant subprojects should
|
||||
be staffed, per the above.
|
||||
|
||||
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
|
||||
[wg-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/wg-governance.md
|
||||
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md
|
||||
[lazy consensus]: http://en.osswiki.info/concepts/lazy_consensus
|
||||
|
||||
[kubernetes-dev@]: https://groups.google.com/forum/#!forum/kubernetes-dev
|
||||
[wg-k8s-infra@]: https://groups.google.com/forum/#!forum/k8s-infra-team
|
||||
[kubernetes/k8s.io]: https://git.k8s.io/k8s.io
|
||||
Loading…
Reference in New Issue