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.
The charter defines the scope and governance of the Multicluster Special Interest Group.
Joining the mailing list for the group will typically add invites for the following meetings to your calendar.
- Regular SIG Meeting: Tuesdays at 9:30 PT (Pacific Time) (bi-weekly). Convert to your timezone.
The Chairs of the SIG run operations and processes governing the SIG.
- Paul Morie (@pmorie)
- Quinton Hoole (@quinton-hoole)
- Slack: #sig-multicluster
- Mailing list
- Open Community Issues/PRs
- GitHub Teams:
- @kubernetes/sig-multicluster-api-reviews - API Changes and Reviews
- @kubernetes/sig-multicluster-bugs - Bug Triage and Troubleshooting
- @kubernetes/sig-multicluster-feature-requests - Feature Requests
- @kubernetes/sig-multicluster-misc - General Discussion
- @kubernetes/sig-multicluster-pr-reviews - PR Reviews
- @kubernetes/sig-multicluster-proposals - Design Proposals
- @kubernetes/sig-multicluster-test-failures - Test Failures and Triage
- Steering Committee Liaison: Antonio Ojea (@aojea)
The following working groups are sponsored by sig-multicluster:
The following subprojects are owned by sig-multicluster:
- Owners:
- Owners:
- Owners: