Connecting Kubernetes clusters with Submariner
summary
Three Kubernetes clusters (one broker + two joined) run on kind on a 20 GB laptop and Submariner is deployed with the subcuttle CLI; it creates CRDs, deploys operators, and opens an IPsec tunnel between selected worker nodes so pod IPs are reachable across clusters. CoreDNS plus the MCS API turns a service-export into a service-import via the broker, DNS resolves remote svc.namespace.svc.cluster domains, and traffic is round-robin across two clusters (cluster-local preference keeps local endpoints). subcuttle shows metrics, latency/throughput benchmarks, and the demo successfully connects pods and services.
AI-written summary · about
chapters (13)
- 0:00Introduction to Submariner
- 0:28Setting up the demo
- 1:24Testing initial connectivity
- 3:05Installing Submariner
- 3:50Deploying the broker
- 5:30Joining clusters
- 8:17Testing cross-cluster connectivity
- 9:26Understanding Submariner components
- 10:44Multi-cluster services API
- 12:20Service discovery behavior
- 14:03Monitoring and tools
- 15:53Prometheus metrics
- 17:17Conclusion and resources
related talks
32mSolving Multi-Cluster Network Connectivity With Submariner
31mHere Be Services: Beyond the Cluster Boundary with Multicluster Servi...
19mMulti-Cluster Service Deployments with Operators and KubeCarrier
45mScaling Microservices Beyond a Single Cluster w/ Kubernetes
29mKubernetes Advanced Networking Testing with KIND
31mSimplifying multi-clusters in Kubernetes using KubeSlice
09mMulti-Cluster Networking: A Technology-Agnostic Network Operator for K8 Federation
21mEdge Deployment of Kubernetes Cluster