SIG-Multicluster Intro and Deep Dive - Jeremy Olmsted

The presentation is about showcasing the AWS cloud map MCS controller for Kubernetes and its interaction with the about API and MCS API.

• The AWS cloud map MCS controller for Kubernetes is showcased in the presentation.
• The controller is built on top of AWS cloud map and interacts with the about API and MCS API.
• The presentation demonstrates the creation of service exports and imports between two EKS clusters.
• The AWS cloud map services created for the namespace are also shown.
• The audience is encouraged to join the bi-weekly meetings of the Sig multi-cluster to provide input and bring up new ideas.

The presenter showcased the creation of service exports and imports between two EKS clusters using the AWS cloud map MCS controller for Kubernetes. The audience was shown how the controller interacts with the about API and MCS API. The presenter also demonstrated the AWS cloud map services created for the namespace. The audience was encouraged to join the bi-weekly meetings of the Sig multi-cluster to provide input and bring up new ideas.

SIG-Multicluster is focused on solving common challenges related to the management of many Kubernetes clusters, across multiple cloud providers (so-called hybrid cloud), and applications deployed across many clusters. In this session, we'll give attendees an overview of the current status of the multi-cluster problem space in Kubernetes and of the SIG. We’ll discuss current thinking around best practices for multi-cluster deployments and what it means to be part of a ClusterSet. Then we’ll highlight current SIG projects, focused use cases, and ideas for what’s next. Most importantly, we’ll provide information on how you can get involved either as a contributor or as a user who wants to provide feedback about the SIG's current efforts and future direction. Bring your questions, problems, and ideas - help us expand the multi-cluster Kubernetes landscape.Click here to view captioning/translation in the MeetingPlay platform!