Federated Services: Straightforward Multicluster
Talkat Linkerd Day Europe 2025 · on Tuesday, 2025-04-01· at 16:30· Level 3 | ICC Capital Suite 14-16·
summary
Federated services merge endpoints from same-named services across clusters into a single load‑balancer pool so one Kubernetes service backend-federated replaces dozens of mirror services (12 clusters in the example). It uses EWMA plus circuit breakers to prefer low‑latency, higher‑capacity endpoints and automatically remove dead endpoints, matching load to capacity; relies on namespace sameness to join services. Feature ships (added November last year), works today, and supports dynamic cluster join/leave while ergonomics are still being improved.
AI-written summary · about
chapters (8)
- 0:00Federated multicluster intro
- 1:47Linkerd multicluster setup
- 5:56Scaling mirror services limits
- 10:14HTTP route load balancing limits
- 13:48EWMA load balancing benefits
- 15:12Federated services concept
- 18:43Federated services future
- 20:30Q&A
related talks
46mUnified Cluster Federation: A Hyperscaled Architecture of...
09mMulti-Cluster Networking: A Technology-Agnostic Network Operator for K8 Federation
27mSimplifying Multi-Cluster Networking With Cilium...
28mMulti-Cluster Service Mesh With Istio
27mCilium Cluster Mesh: The eBPF-Powered Multicluster Solution for Kubernetes
13mWhich Edge Are You on? Service Affinity with Cilium Cluster Mesh
10mLightning Talk: Connecting Klusters on the Edge with Deep Dive into Cilium Cluster Mesh
32mBreaking Boundaries: Multi-cluster with Cilium cluster mesh