linkerd

Linkerd lightweight service mesh. Use for service networking.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

linkerd is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Linkerd lightweight service mesh. Use for service networking.

Teams using linkerd should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/linkerd/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/devops/linkerd/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/linkerd/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How linkerd Compares

Feature / Agent	linkerd	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Linkerd lightweight service mesh. Use for service networking.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Linkerd

Linkerd is a lightweight Service Mesh. It focuses on simplicity and performance (Rust-based proxies). v2.15 (2025) enables **Mesh Expansion** to VMs.

## When to Use

- **Low Overhead**: You want mTLS and Metrics but can't afford Istio's CPU tax.
- **Simplicity**: "It just works". No complex configuration for basic features.
- **Security**: Default-on mTLS and authorization policies.

## Core Concepts

### Micro-Proxy

Linkerd uses a specialized Rust proxy (not Envoy) that is tiny and fast.

### Viz Extension

A dashboard and Prometheus instance pre-configured to show mesh metrics (Success Rate, Latency).

### ServiceProfiles

Define retry logic and timeouts per route.

## Best Practices (2025)

**Do**:

- **Use HA Mode**: Run control plane in high-availability mode for production.
- **Automate Cert Rotation**: Use `cert-manager` to rotate the mTLS root CA automatically.
- **Expand to VMs**: Use the new 2.15 feature to include legacy databases in the mesh.

**Don't**:

- **Don't disable mTLS**: It's verified automatically. Keep it on.

## References

- [Linkerd Documentation](https://linkerd.io/docs/)