linkerd
π―SkillInstallation
npx skills add g1joshi/agent-skills --skill linkerdRun it in a terminal; it asks which AI coding tools to install it for (Claude Code, Codex, Cursor and more).
Uses skills.sh Β· Node.js 22.20+
After installing
Ask for related work and the agent uses it on its own, or call it yourself.
/linkerdInstall by hand
Copy the whole skill folder from GitHub to the place below. Copying only SKILL.md can leave out files the skill uses.
Open the skill folder β- This project
.claude/skills/linkerd/ - All projects
~/.claude/skills/linkerd/
These paths are for Claude Code. For other tools, the command above puts it in the right place.
SKILL.md
View on GitHub βExpert Linkerd service mesh assistance covering ultralight Rust micro-proxies, automatic mTLS, traffic splitting, and zero-config observability. Use when adding secure mTLS and latency metrics to Kubernetes with minimal overhead.
Linkerd
Linkerd is an ultralight, zero-config service mesh written in Rust, providing automatic mutual TLS (mTLS), layer-7 metrics, and transparent traffic shifting without administrative complexity.
When to Use
- Ultralight Kubernetes Service Mesh: High-performance, zero-config microservice mesh written in Rust and Go.
- Automatic Transparent Mutual TLS (mTLS): Instant cryptographically verified encryption between pods without code changes.
- Golden Metrics Collection: Automated latency, traffic volume, and failure rate metrics exposed to Prometheus.
- Traffic Splitting & Progressive Delivery: Canary and blue-green deployments via the Service Mesh Interface (SMI) specification.
Quick Start
# Install Linkerd CLI and check cluster compatibility
curl -fsL https://run.linkerd.io/install | sh
linkerd check --pre
# Install Linkerd control plane into Kubernetes
linkerd install --crds | kubectl apply -f -
linkerd install | kubectl apply -f -
linkerd check
# Inject Linkerd sidecar into an existing namespace
kubectl get deploy -n my-app -o yaml | linkerd inject - | kubectl apply -f -
Core Concepts
Automatic Proxy Injection Annotation
Injecting micro-proxies into deployment pods via annotations:
apiVersion: apps/v1
kind: Deployment
metadata:
name: user-service
namespace: default
annotations:
linkerd.io/inject: enabled # Linkerd proxy automatically injected
spec:
replicas: 2
selector:
matchLabels:
app: user-service
template:
metadata:
labels:
app: user-service
spec:
containers:
- name: app
image: myregistry/user-service:v1.0
ports:
- containerPort: 8080
TrafficSplit for Canary Deployment
Routing canary traffic across distinct service versions:
apiVersion: split.smi-spec.io/v1alpha2
kind: TrafficSplit
metadata:
name: user-service-split
namespace: default
spec:
service: user-service
backends:
- service: user-service-v1
weight: 800m # 80% traffic
- service: user-service-v2
weight: 200m # 20% traffic
Linkerd CLI Diagnostic & Telemetry Inspection
Inspecting real-time traffic statistics between pods:
# Check Linkerd control plane health
linkerd check
# Real-time traffic inspection (Golden Metrics: RPS, Success Rate, Latency P99)
linkerd viz stat deployment -n default
# Trace live traffic calls between services
linkerd viz tap deployment/user-service -n default --to deployment/db-service
Common Patterns
TrafficSplit for Canary Deployment
Problem: Releasing new microservice versions without the risk of impacting 100% of user traffic.
Solution: Use the SMI TrafficSplit custom resource:
apiVersion: split.smi-spec.io/v1alpha2
kind: TrafficSplit
metadata:
name: service-canary-split
namespace: prod
spec:
service: my-service
backends:
- service: my-service-v1
weight: 900
- service: my-service-v2
weight: 100
Best Practices
Do:
- Prefer Linkerd over heavier service meshes when simplicity, low memory (< 30MB/proxy), and ultra-low latency are paramount.
- Run
linkerd checkin CI and post-deployment validation scripts. - Monitor the expiry of Linkerd identity issuer certificates using automated alerts or Cert-Manager.
- Use
linkerd viz tapfor live, real-time debugging of failing requests between pods.
Don't:
- Inject the Linkerd proxy into Kubernetes batch jobs without configuring automated sidecar shutdown.
- Disable mTLS verification; Linkerd enables transparent mTLS out of the box with zero configuration.
- Bypass readiness probes; Linkerd relies on pod health to route mesh traffic.
Troubleshooting
| Error | Cause | Solution |
|---|---|---|
linkerd check: failed to connect to control plane | linkerd-controller pod not running or admission webhook unready. | Run kubectl get pods -n linkerd and verify cluster certificates. |
linkerd-proxy: connection refused to 127.0.0.1 | Application container within pod hasn't finished binding port. | Configure readiness probe on application container. |
Certificates expiring soon warning | Linkerd internal trust anchor or issuer certificate nearing expiry. | Rotate certificates: linkerd upgrade --identity-trust-anchors-file .... |
References
More from this repository10
A template skill providing a starter framework for creating new agent skills with structured sections for triggers, quick start examples, and capability descriptions.
Skill
Skill
Skill
Skill
Skill
Skill
Skill
Skill
Skill