linkerd-patterns

Deploy Linkerd service mesh patterns with mTLS and traffic policies on Kubernetes.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill linkerd-patterns-leonardoteodoroo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linkerd-patterns
Source: https://github.com/leonardoteodoroo/amino-advanced/tree/main/.agent/skills/linkerd-patterns
Command: npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill linkerd-patterns-leonardoteodoroo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implements Linkerd service mesh patterns for lightweight, security-first deployments, enabling easy setup, automatic mTLS, and per-route observability with minimal overhead.

Core Features & Use Cases

  • Lightweight, security-first service mesh for Kubernetes
  • Automatic mTLS across all services
  • TrafficSplit for canary deployments and A/B testing
  • ServiceProfile usage for per-route metrics, retries, and timeouts
  • Support for multi-cluster service mesh

Quick Start

Install Linkerd on your cluster, validate prerequisites, install CRDs and the control plane, and apply the templates to enable mTLS, traffic routing, and metrics.

Frequently Asked Questions about linkerd-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a lightweight service mesh with automatic mTLS in Kubernetes?

To set up a lightweight service mesh with automatic mTLS in Kubernetes, install Linkerd by validating prerequisites, installing CRDs and the control plane, then applying templates to enforce zero-trust networking across all services.

What is the best way to configure traffic splitting for canary deployments in a service mesh?

The best way to configure traffic splitting for canary deployments in a service mesh is using TrafficSplit templates, which enable precise routing and A/B testing across multiple services with minimal overhead.

How do I get per-route metrics, retries, and timeouts for Kubernetes services?

To get per-route metrics, retries, and timeouts for Kubernetes services, apply ServiceProfile configurations within your Linkerd service mesh to define and monitor specific route behaviors.

Can I use a lightweight service mesh for multi-cluster zero-trust networking?

Yes, you can use a lightweight service mesh for multi-cluster zero-trust networking by applying Linkerd patterns that extend automatic mTLS and traffic policies across multiple Kubernetes cluster boundaries.

Do I need to install CRDs before enabling mTLS on my Kubernetes cluster?

Yes, you need to install CRDs before enabling mTLS on your Kubernetes cluster, as the Linkerd control plane requires custom resource definitions to manage ServiceProfiles, TrafficSplits, and multi-cluster support.

What are the limitations of using a lightweight service mesh for traffic policy configuration?

Limitations of using a lightweight service mesh for traffic policy configuration include dependencies on Linkerd's control plane installation, requiring specific CRDs for TrafficSplit and ServiceProfile usage, and multi-cluster support prerequisites.