Linkerd - Service mesh for Kubernetes - 2021
- Description
- Curriculum
- FAQ
- Reviews
A different kind of service mesh
Ultra light, ultra simple, ultra powerful. Linkerd adds security, observability, and reliability to Kubernetes, without the complexity. CNCF-hosted and 100% open source.
Instant platform health metrics
Instantly track success rates, latencies, and request volumes for every meshed workload, without changes or config.
Simpler than any other mesh
Minimalist, Kubernetes-native design. No hidden magic, as little YAML and as few CRDs as possible.
Zero-config mutual TLS
Transparently add mutual TLS to any on-cluster TCP communication with no configuration.
Designed by engineers, for engineers
Self-contained control plane, incrementally deployable data plane, and lots and lots of diagnostics and debugging tools.
Drop-in reliability features
Instantly add latency-aware load balancing, request retries, timeouts, and blue-green deploys to keep your applications resilient.
State-of-the-art ultralight Rust dataplane
Incredibly small and blazing fast Linkerd2-proxy micro-proxy written in Rust for security and performance.
Linkerd is a service mesh for Kubernetes. It makes running services easier and safer by giving you runtime debugging, observability, reliability, and security—all without requiring any changes to your code.
How it works
Linkerd works by installing a set of ultralight, transparent proxies next to each service instance. These proxies automatically handle all traffic to and from the service. Because they’re transparent, these proxies act as highly instrumented out-of-process network stacks, sending telemetry to, and receiving control signals from, the control plane. This design allows Linkerd to measure and manipulate traffic to and from your service without introducing excessive latency.
In order to be as small, lightweight, and safe as possible, Linkerd’s proxies are written in Rust and specialized for Linkerd. You can learn more about the proxies in the Linkerd proxy repo.
MUST TOOL FOR EVERYONE WHO IS WORKING WITH MICROSERVICES SPECIALLY WHEN WORKING WITH KUBERNETES
