Solving Multi-Cluster Network Connectivity With Submariner
Talkat KubeCon + CloudNativeCon North America 2019 · on Thursday, 2019-11-21· at 17:20· Room 15AB - San Diego Convention Center, Mezzanine Level·
summary
Connects Kubernetes clusters at IP-level connectivity by establishing IPSec tunnels between elected gateway nodes, with a central broker cluster stores metadata (cluster IDs, CIDRs, endpoints) and per-cluster route agents that configure node routes. Demo shows pods successfully pinging nginx across OpenShift, Rancher and vanilla clusters (NAT traversal works). Tooling includes a Submariner operator and subctl for deploys; current release fixes encapsulation for lost source IPs and roadmap covers overlapping CIDRs, service discovery and network-policy integration.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:10What is Submariner?
- 2:06How does it work?
- 3:20History of Submariner
- 8:59Roadmap (Overlapping CIDRS)
- 10:09Roadmap (DNS Discovery)
- 11:54Roadmap (Network policies)
- 13:40Deployment Options
- 14:18subtl Deployment
- 15:10Demo time!
- 26:48Community, Q&A
related talks
18mConnecting Kubernetes clusters with Submariner
09mMulti-Cluster Networking: A Technology-Agnostic Network Operator for K8 Federation
36mHybrid Cloud and Multi-Cluster Service Connectivity
46mMulti - Networking Kubernetes Containers with CNI
31mHere Be Services: Beyond the Cluster Boundary with Multicluster Servi...
31mSimplifying multi-clusters in Kubernetes using KubeSlice
36mHybrid Cloud and Multi-Cluster Service Connectivity
36mRemote Control Planes With Konnectivity; What, Why And How?