Service Mesh & Kubernetes Multicluster Communication With Linkerd
summary
Linkerd is shown handling cross‑cluster pod‑to‑pod traffic by creating a mirrored ClusterIP service in the remote cluster and routing requests through a Linkerd gateway behind a load balancer, with authorization enforced and mTLS with a shared root CA for identity. The demo builds gateway and mirror resources, forwards traffic to the original backend, and exposes observability with p99/p995 metrics on the Linkerd dashboard, proving the multicluster path works end to end.
AI-written summary · about
chapters (9)
- 0:00Welcome and introduction
- 1:04What is a service mesh
- 3:34Challenges without service mesh
- 5:20How service mesh helps
- 6:23Linkerd overview
- 6:44Multicluster communication
- 8:27Security with mutual TLS
- 9:51Demo of multicluster setup
- 11:24Closing and thanks
