Submariner
Container networking software
DevOps software
Containerization software
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
Take the quiz to check if Submariner and its alternatives fit your requirements.
Completely free
Free Trial unavailable
Free version
Small
Medium
Large
-
What is Submariner
Submariner is an open-source Kubernetes-focused networking project that connects multiple Kubernetes clusters to enable cross-cluster pod and service connectivity. It targets platform and DevOps teams that run multi-cluster or hybrid environments and need network-level communication between workloads across clusters. Submariner typically works with common Kubernetes CNI implementations and uses components such as a gateway and service discovery to route traffic between clusters. It is commonly deployed as part of a broader multi-cluster operations approach rather than as a full Kubernetes distribution.
Multi-cluster connectivity focus
Submariner is purpose-built to provide L3/L4 connectivity between Kubernetes clusters, including cross-cluster service access. This directly addresses scenarios where teams operate multiple clusters for isolation, geography, or lifecycle reasons. It complements cluster-level networking by extending reachability across cluster boundaries. The project’s scope stays centered on multi-cluster networking rather than general ingress or service mesh features.
Works with Kubernetes CNIs
Submariner is designed to integrate with Kubernetes environments that already use a CNI plugin, reducing the need to replace existing cluster networking. This can simplify adoption in environments where the CNI choice is standardized. It focuses on inter-cluster routing and service discovery while leaving intra-cluster networking to the existing CNI. This separation can help teams keep responsibilities and troubleshooting domains clearer.
Open-source and portable
Submariner is available as an open-source project and can be deployed across different Kubernetes environments, including on-premises and cloud. This supports vendor-neutral multi-cluster designs where clusters run on different infrastructures. Teams can inspect and modify the code and deployment manifests to meet internal requirements. It can be evaluated without commercial licensing constraints.
Operational complexity in production
Multi-cluster networking introduces additional components (for example, gateways and service discovery) that must be deployed, monitored, and upgraded. Troubleshooting cross-cluster traffic can be more complex than single-cluster networking due to more hops and more failure domains. Teams often need strong Kubernetes networking expertise to operate it reliably. This can increase the operational burden compared with simpler single-cluster networking setups.
Not a full platform
Submariner focuses on cross-cluster connectivity and does not replace broader Kubernetes platform capabilities such as cluster lifecycle management, policy governance, or full application delivery workflows. Organizations typically pair it with other tools for CI/CD, ingress, and runtime security. Buyers looking for an integrated end-to-end platform may find they still need multiple additional components. This can complicate procurement and architecture decisions.
Feature scope differs from meshes
Submariner primarily addresses network connectivity and service reachability across clusters rather than application-layer traffic management. Capabilities commonly associated with service meshes—such as L7 routing, fine-grained traffic splitting, and deep telemetry—are not its core focus. Teams needing those controls may need additional tooling on top. This can lead to overlapping networking layers if not carefully designed.
Seller details
Cloud Native Computing Foundation (CNCF), a project of the Linux Foundation
San Francisco, CA, USA
2015
Non-profit
https://kubernetes.io/
https://x.com/kubernetesio
https://www.linkedin.com/company/cloud-native-computing-foundation/
