linkerd-patterns

Traffic splitting for canary deployments uses Kubernetes manifests like TrafficSplit to route a percentage of traffic to a new version. This configures Linkerd resources to gradually shift traffic from a stable version to a canary release.

Automatic mTLS in a Linkerd service mesh secures pod-to-pod communication by encrypting traffic without requiring application code changes. This applies lightweight proxies to handle mutual TLS automatically across Kubernetes networking.

Implementing zero-trust networking with server authorization policies restricts which clients can connect to specific servers. This configures Linkerd Server and ServerAuthorization manifests to enforce access control over mTLS-secured traffic.

Per-route metrics for Kubernetes services require configuring service profiles to define specific HTTP routes. This generates Linkerd service profile manifests to unlock detailed observability and traffic monitoring for individual endpoints.

Checking cluster pre-installation requirements before setting up a Linkerd service mesh ensures your Kubernetes environment meets compatibility standards. This utilizes Linkerd CLI commands to validate cluster readiness for lightweight deployment.

Using Linkerd for A/B testing without modifying application code is possible by configuring traffic management manifests at the mesh layer. This sets up TrafficSplit resources to control routing distributions for different service versions.