Submariner enables direct networking between Pods and Services in different Kubernetes clusters, either on-premises or in the cloud.
As Kubernetes gains adoption, teams are finding they must deploy and manage multiple clusters to facilitate features like geo-redundancy, scale, and fault isolation for their applications. With Submariner, your applications and services can span multiple cloud providers, data centers, and regions.
Submariner is completely open source, and designed to be network plugin (CNI) agnostic.
Submariner Provides: cross-cluster L3 connectivity using encrypted VPN tunnels; service Discovery across clusters; subctl, a friendly deployment tool; support for interconnecting clusters with overlapping CIDRs
2. Oleg Chunikhin
CTO, Kublr
• 25 years in software architecture & development
• Working w/ Kubernetes since its release in 2015
• Software architect behind Kublr—an enterprise
ready container management platform
• @olgch
Introductions
9. Submariner Components
● Broker
○ No active components; ns used to exchange connection info
● Gateway Engine (managed by operator)
○ Gateway management, failover, reconnection, LB, routing
○ gateway, route agent
● Service discovery (managed by operator)
○ Services export and import
○ lighthouse agent, lighthouse coredns
10. Submariner Responsibilities
● Broker and operator
○ Share and coordinate connection info between clusters
● Gateway Engine (managed by operator)
○ (Re-)configure routes on each node on changes in
■ peered clusters
■ active gateway
■ imported/exported services
○ Failover gateways
○ (Re-)connect
○ Load balancing
● Service discovery (managed by operator)
○ Share service import/export information
○ Serve DNS requests for clusterset.local domain