SIG Multicluster charter

This commit is contained in:
Paul Morie 2018-08-20 12:07:08 -04:00
parent f0936cfcdd
commit 8242f914ce
3 changed files with 50 additions and 1 deletions

View File

@ -10,6 +10,8 @@ To understand how this file is generated, see https://git.k8s.io/community/gener
A Special Interest Group focused on solving common challenges related to the management of multiple Kubernetes clusters, and applications that exist therein. The SIG will be responsible for designing, discussing, implementing and maintaining APIs, tools and documentation related to multi-cluster administration and application management. This includes not only active automated approaches such as Cluster Federation, but also those that employ batch workflow-style continuous deployment systems like Spinnaker and others. Standalone building blocks for these and other similar systems (for example a cluster registry), and proposed changes to kubernetes core where appropriate will also be in scope.
The [charter](charter.md) defines the scope and governance of the Multicluster Special Interest Group.
## Meetings
* Regular SIG Meeting: [Tuesdays at 9:30 PT (Pacific Time)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9:30&tz=PT%20%28Pacific%20Time%29).
* [Meeting notes and Agenda](https://docs.google.com/document/d/18mk62nOXE_MCSSnb4yJD_8UadtzJrYyJxFwbrgabHe8/edit).

View File

@ -0,0 +1,47 @@
# SIG Multicluster Charter
This charter adheres to the conventions described in the [Kubernetes Charter README] and uses
the Roles and Organization Management outlined in [sig-governance].
## Scope
The scope of SIG Multicluster is limited to the following subprojects:
- The [cluster-registry](https://github.com/kubernetes/cluster-registry)
- Kubernetes federation:
- [Federation v2](https://github.com/kubernetes-sigs/federation-v2)
- [Federation v1](https://github.com/kubernetes/federation)
- [Kubemci](https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress)
### In scope
See [SIG README].
#### Code, Binaries and Services
SIG Multicluster code and binaries are limited to those from one of the SIG subprojects.
#### Cross-cutting and Externally Facing Processes
- Consult with other SIGs and the community on how the in-scope mechanisms
should work and integrate with other areas of the wider Kubernetes ecosystem
### Out of scope
- Software that creates or manages the lifecycle of Kubernetes clusters
## Roles and Organization Management
This sig follows adheres to the Roles and Organization Management outlined in [sig-governance]
and opts-in to updates and modifications to [sig-governance].
### Subproject Creation
SIG Multicluster delegates subproject approval to Technical Leads. See [Subproject creation - Option 1].
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
[sig-subprojects]: https://github.com/kubernetes/community/blob/master/sig-multicluster/README.md#subprojects
[sigs.yaml]: https://github.com/kubernetes/community/blob/master/sigs.yaml#L1042
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md
[Subproject creation - Option 1]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md#subproject-creation
[SIG README]: https://github.com/kubernetes/community/blob/master/sig-multicluster/README.md

View File

@ -1090,7 +1090,7 @@ sigs:
systems like Spinnaker and others. Standalone building blocks for these and other
similar systems (for example a cluster registry), and proposed changes to kubernetes
core where appropriate will also be in scope.
charter_link:
charter_link: charter.md
label: multicluster
leadership:
chairs: