SIGs

• sig-api-machinery
• sig-apps
• sig-architecture
• sig-auth
• sig-autoscaling
• sig-aws
• sig-azure
• sig-big-data
• sig-cli
• sig-cloud-provider
• sig-cluster-lifecycle
• sig-cluster-ops
• sig-contributor-experience
• sig-docs
• sig-gcp
• sig-ibmcloud
• sig-instrumentation
• sig-multicluster
• sig-network
• sig-node
• sig-openstack
• sig-product-management
• sig-release
• sig-scalability
• sig-scheduling
• sig-service-catalog
• sig-storage
• sig-testing
• sig-ui
• sig-vmware
• sig-windows

Multicluster Special Interest Group

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 API’s, 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.

Meetings

• Regular SIG Meeting: Tuesdays at 9:30 PT (Pacific Time) (biweekly). Convert to your timezone.

  • Meeting notes and Agenda.
  • Meeting recordings.

• Federation v2 Working Group: Wednesdays at 9:30 PT (Pacific Time) (weekly). Convert to your timezone.

  • Meeting notes and Agenda.
  • Meeting recordings.

Leadership

Chairs

The Chairs of the SIG run operations and processes governing the SIG.

• Christian Bell (@csbell), Google
• Quinton Hoole (@quinton-hoole), Huawei

Contact

• Slack
• Mailing list
• Open Community Issues/PRs

Subprojects

The following subprojects are owned by sig-multicluster:

• federation-v1

  • Owners:
  • https://raw.githubusercontent.com/kubernetes/federation/master/OWNERS

• federation-v2

  • Owners:
  • https://raw.githubusercontent.com/kubernetes-sigs/federation-v2/master/OWNERS

• cluster-registry

  • Owners:
  • https://raw.githubusercontent.com/kubernetes/cluster-registry/master/OWNERS

• kubemci

  • Owners:
  • https://raw.githubusercontent.com/GoogleCloudPlatform/k8s-multicluster-ingress/master/OWNERS

GitHub Teams

The below teams can be mentioned on issues and PRs in order to get attention from the right people. Note that the links to display team membership will only work if you are a member of the org.

The google groups contain the archive of Github team notifications. Mentioning a team on Github will CC its group. Monitor these for Github activity if you are not a member of the team.

Subprojects

Federation v2

Control Plane for newer Multicluster-specific APIs. Discussions are ongoing to focus future development on multi-cluster specific Kubernetes APIs rather than a reimplementation of single-cluster Kubernetes APIs.

Cluster Registry

Common abstraction for a Registry of Clusters that can store per-Cluster metadata and supports Kubernetes label selection. The Cluster Registry can be deployed as a standalone or an aggregated API server and currently provides a Registry of Clusters without any actively reconciling Kubernetes controller. The API design is documented here and is intended to serve as a basis to develop multicluster controllers.

Kubemci (Kube Multi-cluster Ingress)

Ability to program Global multicluster load balancers with two deliverables:

• Standalone CLI tool without a centralized control plane. Allows ingress configurations that span multiple clusters. It needs to be invoked whenever there is a change in the number of clusters (healthchecking is still maintained in the background). Much of this work will be folded back into the next deliverable.
• Kubernetes style multicluster API and self-healing controller with cluster registry

Federation v1 (a.k.a. Cluster Federation)

Control Plane that coordinates configuration across multiple clusters by presenting a subset of the existing single-cluster Kubernetes APIs. Initially released as part of Kubernetes 1.3, Cluster Federation has implemented parts of the existing “single-cluster” Kubernetes API so that they may be used transparently in a multi-cluster fashion. As of Kubernetes 1.9, many of the non-Federated Kubernetes Workloads APIs have moved to GA (Deployments, ReplicaSets, Daemonset, StatefulSet). However, under Federation, these workloads have not reached the maturity of “GA” since they are re-implemented by different federated controllers. The SIG is currently re-thinking how to support Kubernetes APIs in a Federation fashion and this discussion is reflected under Federation v2.