1 of 9

SIG Multicluster

Community Meeting Update

​

2 of 9

What we did last cycle

  • Community consensus what we call a group of clusters
    • ClusterSet
  • Some basic guidelines for multi-cluster deployments
    • Namespace Sameness
  • Kubefed
  • Multi-cluster service APIs alpha release in SIGs repo
    • sigs.k8s.io/mcs-api

​

3 of 9

Plans for upcoming cycles

  • Further define what we want to do with ClusterSets
    • Membership (Registration?)
    • Workload placement
  • Refine the concept of a “cluster identity”
  • Kubefed continues
  • Multi-Cluster Service APIs -> Beta -> GA

​

4 of 9

Kubefed

Currently considering how to add pull reconciliation

  • Touches cluster registry concept
  • How does a pull reconciler running in a remote cluster gain access to observe the cluster where kubefed API surface exists?

Shout out to Jimmi, Hector and others from D2IQ for helping move the project forward

5 of 9

Multi-Cluster Service APIs

KEP 1645

Alpha release at sigs.k8s.io/mcs-api

Things to do before beta:

  • Multi-Cluster DNS spec
  • NetworkPolicy
  • Define Cluster ID

​

6 of 9

Work API

  • Early stages currently
  • Some prototyping has been done
  • Initial KEP in draft
  • Thanks Vallery Lancey and Jian Qiu for driving this!

7 of 9

We need your input

  • What else should expand to the ClusterSet?
  • What should we focus on next?
  • How can your projects cross the cluster boundary?
  • What have you already built that you liked? What can you share with us?
  • SIG-Network - help us make sure MCS evolves with cluster-local services

8 of 9

How you can contribute

Come to our meetups (Tuesday 9:30-10:20 Pacific)

Add a topic to the meeting agenda: https://goo.gl/PhyWjj

Ask questions in the forum or on slack: #sig-multicluster

9 of 9

Where to find us