Multi-Cluster is Easier Than You Think with Linkerd and Ambassador
Talkat KubeCon + CloudNativeCon North America 2020 Virtual · on Thursday, 2020-11-19· at 14:55· Intrado Virtual Event Platform,·
summary
Concrete howto for connecting two Kubernetes clusters (GKE + Docker Desktop) using Linkerd and Ambassador with working demo of a Linkerd service mirror that creates podinfo-east in West, an Ambassador gateway used as the routable endpoint, and mTLS via a shared trust anchor generated with step CLI. Endpoints point at the Ambassador load balancer IP rather than pod IPs, traffic splits use SMI at 50/50 traffic split, and use cases include cluster isolation, disaster recovery, and developer offloading.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:48What is MultiCluster
- 2:25Demo Overview
- 3:47Demo Setup
- 8:05Overview
- 8:47Service Discovery
- 9:40Pod Info Service
- 12:22Endpoint Resource
- 12:38Kubernetes Endpoint Controller
- 14:24Ambassador
- 18:52Ambassador Gateway
- 19:14Request Routing
- 19:31Split Traffic
- 25:11Summary
- 25:45Cluster Isolation
- 26:18Disaster Recovery
- 26:46Development
- 27:28Community Anchor Program
- 27:51Join our communities
related talks
12mService Mesh & Kubernetes Multicluster Communication With Linkerd
01h 31mMulti-cluster Failover Using Linkerd
18mAbstracting Multi-Cluster Topologies With CAPI and Linkerd for Internal Developer Platforms
50mMulti-Cluster Kubernetes and Service Mesh Patterns
31mHere Be Services: Beyond the Cluster Boundary with Multicluster Servi...
42mSIG Multi-Cluster Deep Dive
36mKubernetes Multi-Cluster Made Easy - Federica Ciuffo and Marco Ballerini
32mK8s-based API Gateway