submariner-io/submariner
Networking component for interconnecting Pods and Services across Kubernetes clusters. observed · 2026-08-28
Health v2 · maintenance only
96/100
- Activity 99
- Release rhythm 91
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 18.0
- age_days: 2732
- days_rel: 63
- days_push: 7
- n_releases_24m: 27
Adoption not part of the score
2686 stars · 212 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Submariner is a CNCF sandbox tool that interconnects the overlay networks of multiple Kubernetes clusters, enabling direct Pod-to-Pod and Service-to-Service IP reachability across clusters on-premises or in the cloud. It provides encrypted or unencrypted tunnels (IPsec, WireGuard, VXLAN), cross-cluster DNS service discovery via Lighthouse, and Globalnet support for clusters with overlapping CIDRs.
Use cases
- connect pods across multiple kubernetes clusters
- multi-cluster service discovery with dns
- network clusters with overlapping cidrs
- encrypted tunnels between kubernetes clusters on different clouds
- hybrid cloud and on-premises cluster networking
- expose a kubernetes service to other clusters
- multi-cluster applications spanning regions and providers
When to choose
- you need direct L3 connectivity between Pods and Services in different Kubernetes clusters
- your clusters span multiple cloud providers, data centers, or regions
- you need cross-cluster DNS-based service discovery following Kubernetes Multi-Cluster Services APIs
- your clusters have overlapping Pod/Service CIDRs and you cannot change them
- you want a CNI-agnostic solution with pluggable cable drivers (IPsec, WireGuard, VXLAN)
When to avoid
- you only have a single Kubernetes cluster
- you need application-layer (L7) routing or API aggregation rather than flat L3 connectivity
- you want a fully managed multi-cluster solution and prefer vendor offerings like Anthos or Azure Arc
- your gateway nodes lack IP reachability between clusters and you cannot open the required ports
Facets
application · maturity active
networking security service-discovery deployment cli networking cloud-computing microservices go cloud self-hosted multi-cluster kubernetes-networking cross-cluster-connectivity ipsec wireguard vxlan cni-agnostic service-discovery globalnet lighthouse cnfc-sandbox subctl containers devops kubernetes docker linux
10 sources
- readme: https://github.com/submariner-io/submariner · fetched 2026-08-28 · 0fa24c59daf8
- homepage: https://submariner.io · fetched 2026-08-29 · 477303915138
- site_page: https://submariner.io/getting-started · fetched 2026-08-29 · 4e4e8bd22d4e
- site_page: https://submariner.io/getting-started/architecture · fetched 2026-08-29 · 869537df97a7
- site_page: https://submariner.io/getting-started/architecture/broker · fetched 2026-08-29 · 746a0ca0390c
- site_page: https://submariner.io/getting-started/architecture/gateway-engine · fetched 2026-08-29 · 668046ad442b
- site_page: https://submariner.io/getting-started/architecture/service-discovery · fetched 2026-08-29 · dee6fcf1a83e
- site_page: https://submariner.io/getting-started/architecture/globalnet · fetched 2026-08-29 · ff175d603d58
- site_page: https://submariner.io/getting-started/architecture/networkplugin-syncer · fetched 2026-08-29 · e40da174db12
- site_page: https://submariner.io/getting-started/architecture/networkplugin-syncer/ovn-kubernetes · fetched 2026-08-29 · c62fffc223f6
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| submariner-io/submariner | main | 96 |
For agents
markdown · JSON · MCP: product_card(name="submariner-io/submariner")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem