Kubernetes Cluster Federation: How to Write a Federated Controller? [A]
summary
Explains how to write a federated controller using the informer library, the federated informer helper, and a deletion helper that uses the finalizer API; shows the reconciler functions that list‑and‑copy objects from the Federation API to member clusters and handle cluster join/leave events. Demonstrates a foo controller and kubefed tooling against two GCE clusters, with creates, auto‑recreation after node deletes, and cascading delete working end‑to‑end. Mentions federated ingress, replicas, namespaces, secrets, configmaps and alpha deployments and kubefed becoming beta in 1.6.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:22What is Cluster Federation
- 3:01How it works
- 4:11Architecture
- 5:06Control Plane
- 6:26Why write a Federated Controller
- 9:24Federated Controller Architecture
- 11:48API Types
- 13:38Informer Library
- 16:48Cascading Deletion
- 19:48Demo
related talks
46mCluster Federation in Kubernetes: Past, Present and the Future
40mDeep Dive: Kubernetes SIG Multicluster
34mKubernetes Multi-Cluster Operations without Federation
01h 02mIntro + Deep Dive: Multicluster SIG
35mKubernetes Multicluster SIG
25mKubernetes Scalability: Federation & Cluster API - Katie Gamanji, Condé Nast International
14mKubernetes Federation for Edge
35mKubernetes Multicluster SIG
