Multi-cluster Failover Using Linkerd
summary
Walks through a hands‑on setup: two Kubernetes clusters (east/west) each run Linkerd control planes in HA (3 replicas), install Linkerd multi-cluster (gateway + service‑mirror), enable the viz extension for Prometheus metrics, and apply an SMI TrafficSplit to shift traffic (example moved from 75/25 to 0/100). The failover extension monitors service endpoints and automatically redirects requests when a service is scaled to zero, all secured end‑to‑end with mutual TLS.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 4:22Multicluster Failover
- 6:50What is Linkerd
- 11:59Architecture
- 16:23Setup
- 23:23Security
- 32:30Deploy
- 38:41Linkerdvis
- 47:05Troubleshooting
- 51:01Metrics
- 52:21Deploy Multicluster Extension
related talks
12mService Mesh & Kubernetes Multicluster Communication With Linkerd
28mMulti-Cluster is Easier Than You Think with Linkerd and Ambassador
35mDeep Dive: Linkerd
09mUsing Service Mesh in Multi-Cluster Kubernetes Environment for DR Use Case
28mOverview and State of Linkerd
50mMulti-Cluster Kubernetes and Service Mesh Patterns
18mAbstracting Multi-Cluster Topologies With CAPI and Linkerd for Internal Developer Platforms
37mBuilding the Multi-Cluster L7 Load Balancer