Linkerd vs Network Service Mesh
Linkerd
linkerd.ioNetwork Service Mesh
networkservicemesh.ioSide by side
| Figure | Linkerd | Network Service Mesh |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Service Mesh Platforms | 7.6 (#10) | 8.4 (#3) |
| Governance | Linkerd is a CNCF graduated project licensed under Apache 2.0. | Project governance prioritizes community over product or company and says contributors participate as individuals. |
Plans
In their own words
Linkerd
Linkerd is a service mesh for Kubernetes that adds runtime debugging, observability, reliability and security without requiring changes to application code. It installs into a Kubernetes cluster and injects sidecar proxies into workload pods. The mesh handles HTTP, HTTP/2, gRPC and arbitrary TCP traffic, including TLS connections and WebSockets. It automatically enables mutual TLS between meshed applications and supports authorization policies between services. Metrics include request volume, success rates and latency distributions for HTTP, HTTP/2 and gRPC, plus TCP-level metrics. Traffic controls include load balancing, retries, timeouts, dynamic routing, traffic splitting and rate limiting. Linkerd can use Prometheus and Grafana and supports distributed tracing. Its Linkerd Viz Prometheus instance retains metrics for a short fixed interval, currently six hours, so it is intended to supplement an existing metrics store. Installation requires a modern Kubernetes cluster and a working kubectl command. The open-source project is licensed under Apache 2.0; Buoyant offers commercial support, training and architecture reviews. The listed plan is free.
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.