Cluster Federation Basics
What you'll learn: How to coordinate Kubernetes workloads across multiple independent clusters using federation or multi-cluster tools.
Why Federation Matters
When you manage multiple Kubernetes clusters—perhaps spread across different regions, cloud providers, or data centers—you face a coordination challenge. Each cluster operates independently, but you often want consistent deployments, unified DNS, or shared configurations across all of them. Cluster federation provides a control layer that sits above individual clusters, letting you manage them as a logical group.
How Federation Works
Think of federation like a corporate headquarters coordinating multiple branch offices. The headquarters (federation control plane) doesn't replace local management at each branch (individual cluster control planes)—it synchronizes policies, configurations, and workloads across them.
Key capabilities include:
- Cross-cluster resource propagation: Deploy a single manifest that gets distributed to selected clusters
- Multi-cluster DNS: Services automatically discoverable across clusters with federated DNS names
- Multi-cluster scheduling: Workloads placed based on cluster capacity, location, or policies
- Unified configuration: ConfigMaps, Secrets, and Namespaces synchronized across clusters
Common Tools
While the original Kubernetes Federation v1 is deprecated, modern approaches include:
- KubeFed (Federation v2): Community project for declarative multi-cluster management
- Service meshes: Istio, Linkerd for cross-cluster service communication
- GitOps tools: ArgoCD, Flux with multi-cluster support
- Cloud-native solutions: GKE Hub, AWS EKS Anywhere, Azure Arc
You typically don't federate everything—only resources that need cross-cluster consistency or availability.
Key Takeaway: Cluster federation provides centralized coordination for multiple independent Kubernetes clusters, enabling consistent deployments and cross-cluster service discovery without eliminating each cluster's autonomy.