Kubernetes Multi-Cluster Operations without Federation
summary
Enterprises run about 5–10 clusters on average and Federation as-is creates a root‑level blast radius and single point of failure. The practical alternative is a CRD‑backed cluster registry plus a sync policy implemented by lightweight agents that use a read only pull model to apply RBAC, quotas and namespaces, with operators for workload workflows, and examples ranging from bash loops to Jenkins pipelines and an open source operator framework. Federation v2 uses CRDs with template, placement and override subresources.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:43Everybody is running multiple clusters
- 1:36What is Federation
- 7:53Cluster Registry
- 10:25Custom Workflows
- 15:39Scenarios
- 19:32Where do we go
- 22:19MultiCluster Ingress
- 23:45Operator Pattern
- 27:41Federation v2
- 30:14Kubernetes Native
- 31:36Takeaway
related talks
40mDeep Dive: Kubernetes SIG Multicluster
19mKeynote: Kubernetes Federation
46mCluster Federation in Kubernetes: Past, Present and the Future
09mMulti-Cluster Networking: A Technology-Agnostic Network Operator for K8 Federation
31mThe OpenShift federation: how to manage multiple Kubernetes clusters
39mMulti-Cluster Ops in a Hybrid World
01h 02mIntro + Deep Dive: Multicluster SIG
30mHow to Coordinate Your Multi-cluster Kubernetes Environment with Ease