Why Linkerd
Linkerd is the lightest Kubernetes service mesh — written in Rust, ~10MB per proxy. Get mTLS, observability, and reliability features without the complexity of Istio.
Install
curl --proto '=https' -sSfL https://run.linkerd.io/install | sh
linkerd install --crds | kubectl apply -f -
linkerd install | kubectl apply -f -
linkerd check
Mesh Your Application
kubectl get deploy -n myapp -o yaml | linkerd inject - | kubectl apply -f -
One command. Automatic mTLS, metrics, retries.
Observability
linkerd viz install | kubectl apply -f -
linkerd viz dashboard
# Per-route metrics
linkerd viz routes deploy/web -n myapp
Traffic Split
apiVersion: split.smi-spec.io/v1alpha4
kind: TrafficSplit
metadata:
name: web-split
spec:
service: web
backends:
- service: web-v1
weight: 900
- service: web-v2
weight: 100
Key Features
- Rust proxies — ~10MB, microsecond latency overhead
- Automatic mTLS — zero-config encryption
- Golden metrics — success rate, latency, throughput per service
- Retries and timeouts — configurable per route
- Multi-cluster — service mirroring across clusters
- CNCF Graduated — battle-tested
Linkerd vs Istio
| Feature | Linkerd | Istio |
|---|---|---|
| Proxy | Rust (linkerd2-proxy) | Envoy (C++) |
| Memory per pod | ~10MB | ~50-100MB |
| Complexity | Simple | Complex |
| mTLS | Automatic | Automatic |
| L7 policies | Basic | Advanced |
Resources
Need to extract service mesh data, traffic metrics, or cluster topology? Check out my Apify tools or email spinov001@gmail.com for custom solutions.
Top comments (0)