Fast and Furious Multi-Cloud Connectivity
summary
Architecture shows Kubernetes clusters in AWS GCP and Azure connected with either VPN or private links (Direct Connect Interconnect ExpressRoute via Megaport or colocation routers) using BGP and Transit/Transit‑Network patterns; goal is sub‑5 ms RTT for CockroachDB/NATS. Tests with netperf iperf and Fortio across pod‑to‑pod and node‑to‑node show VPN P99 ≈ 10–12 ms with 100 ms spikes, direct links cut P99 to ~4–6 ms. Cilium cluster‑mesh provides GlobalServices and L7 policy but no same‑node encryption. Azure routing and prefix limits (200) and TGW limits require workarounds; solution works but needs region‑specific tuning.
AI-written summary · about
chapters (6)
- 0:00Start
- 7:16Star Wars Demo
- 31:42"Default" Configuration Routing
- 34:34Performance Tests
- 39:43Kubernetes Network Model - Overlay Network Example
- 40:25Container Network Interface (CNI)
related talks
52mFast and Furious Multi-Cloud Connectivity
24mConfluent's Multi-Cloud Journey to Cilium: Pitfalls and Lessons Learned
33mCheap Routes, Fast Paths & Keeping Track
26mScaling Multi-cluster Kubernetes at Teleport Cloud
34mLow Latency Multi-cluster Kubernetes Networking in AWS
29mBuild resilient and secure global cloud networks
27mChoosing Cloud Native Technologies for the Journey to Multi-cloud
31mConnect your network to AWS with hybrid connectivity solutions