Introduction To Cluster API
summary
Kubernetes Cluster API (CAPI) provides a declarative, GitOps-friendly control plane that reconciles clusters via controllers, webhooks and CRDs and enforces ordering so workers cannot upgrade before control plane. It uses pluggable providers: infrastructure, control-plane and bootstrap (examples: Hetzner-style infra, kubeadm bootstrap, control plane as pods in the management cluster). MachineDeployment behaves like a pod Deployment and MachineHealthCheck remediates offline nodes after ~10 minutes. ClusterClass/templating standardize multi-cluster fleets.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:09What is Cluster API
- 2:58Centralized cluster management
- 5:53Cluster API providers
- 8:20Core concepts
- 12:56YAML configuration example
- 17:36Day-two operations
- 21:34Health checks
- 22:43Workload management
- 24:08Summary
related talks
25mCluster API: IaC for Kubernetes
39mCluster API & Cluster Autoscaler
36mUnderstanding Cluster-API Structure via the OpenStack Provider
46mSIG Cluster Lifecycle (Cluster API)
06mSponsored Keynote: Recursive Kubernetes: Cluster API and Clusters as Cattle
32mCluster API as Code
42mDeep Dive: Cluster Lifecycle SIG (Cluster API)
30mBuild Your Own Cluster API Provider the Easy Way