Liqo vs Network Service Mesh
Liqo
liqo.ioNetwork Service Mesh
networkservicemesh.ioSide by side
| Figure | Liqo | Network Service Mesh |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · Container Networking Software | 7.1 (#18) | 8.3 (#3) |
| License | The official site says Liqo is licensed under Apache-2.0. | The public Network Service Mesh GitHub repositories shown are licensed Apache-2.0. |
| Purpose | Liqo is an open-source project for creating dynamic Kubernetes multi-cluster topologies across on-premise, cloud, and edge infrastructures. | Network Service Mesh is a hybrid and multi-cloud IP service mesh for connecting workloads across clusters and clouds. |
Plans
In their own words
Liqo
Liqo connects Kubernetes clusters into multi-cluster topologies, allowing them to share namespaces, resources, and workload capacity. It can extend consumer namespaces and replicate configurations, secrets, services, and other resources. A remote cluster appears as a virtual node, so the consumer cluster can schedule workloads there. Liqo’s network fabric connects pods across peered clusters using WireGuard VPN tunnels by default, and it describes cross-cluster storage support for stateful workloads. Peering can be declared with Kubernetes resources and managed through GitOps tools such as ArgoCD. The liqoctl CLI installs and uninstalls Liqo, manages peering, configures namespace-level offloading, and reports status. Liqo targets heterogeneous on-premises, public cloud, edge, and multi-cloud environments, with support listed for Kubernetes, Kubeadm, K3s, K0s, AKS, EKS, GKE, Aruba Cloud KaaS, and OpenShift. It is free and open source under Apache-2.0. Liqo requires Linux kernel 5.10 or later and recommends at least 2 CPUs and 2 GB of RAM for a cluster.
Network Service Mesh
Network Service Mesh connects workloads across clusters and clouds through a hybrid, multi-cloud IP service mesh. Each workload can connect independently to zero or more Network Services, regardless of where it runs. The project says it works with an existing CNI without requiring changes to Kubernetes or workloads. Services can provide connectivity, security, and observability at Layer 3 and above, carrying IP or Ethernet payloads.
Clients may be Kubernetes pods, virtual machines, or physical servers. They authenticate independently, currently using SPIFFE IDs, and need authorization to attach. Clients request and close virtual wires over gRPC and can monitor connection status through a streaming call. Endpoint selection offers composition, selective composition, topology awareness, and scale from zero. A service may also provide domain-scoped DNS for connected pods. The architecture describes integration with Istio, Linkerd, Consul, and Kuma. Network Service Mesh is a CNCF sandbox project and is free and open source. Its run guide lists Docker, Go, a Kubernetes cluster, and kubectl as prerequisites; most examples require at least two worker nodes.