Skip to main content
Account

Submariner

Submariner connects Pods and Services across Kubernetes clusters. Learn how gateways, the Broker, Lighthouse and Globalnet enable cross-cluster networking.

Status
Stable
Category
Runtime
Subcategory
Cloud Native Network
License
Apache-2.0
Technology matrix Skip Just not for me See the matrix

Submariner provides flat Layer 3 connectivity and cross-cluster service discovery between Kubernetes clusters, including clusters that live in different clouds, VPCs, or on-premises networks with overlapping or non-overlapping CIDRs. It lets a pod in cluster A reach a service in cluster B by its DNS name, as if they were in the same cluster.

Architecturally, Submariner elects a Gateway node in each participating cluster that terminates an encrypted tunnel (IPsec via Libreswan or WireGuard) to the other clusters’ gateways. A Route Agent on every node programs the data path so pod and service traffic destined for remote CIDRs is routed through the local gateway. The Broker is a lightweight coordination point (itself a Kubernetes cluster) that shares endpoint and service information across members. Lighthouse extends CoreDNS with the clusterset.local domain defined by the Kubernetes multi-cluster services API so services can be exported and consumed by name. Globalnet handles the overlapping-CIDR case by NATing traffic through a virtual global CIDR.

Submariner is a CNCF Sandbox project originated at Rancher/SUSE and is commonly used for hybrid-cloud failover, regulated multi-region deployments, and federating clusters managed by Red Hat Advanced Cluster Management.

Cloud Native Network

Email signup loads here. You can also manage email preferences in account settings.

Build Submariner? I'll show you where engineers get stuck with it β†’ Back free content for the community β†’