Bare-Metal Chronicles: Intertwinement of Tinkerbell, Cluster API and GitOps
summary
Cluster API, Tinkerbell and the kpt provider are shown wired together so YAML CRDs declare clusters and Tinkerbell templates/ workflows provision bare‑metal hardware; Argo CD watches Helm values to change replicas. Demo runs on kind + AWS (uses kubeadm bootstrap and CAPA controllers) and increases worker replicas from 1 to 5 via a git commit; new machines appear within about a minute so the automation actually works. Cluster API provider for Tinkerbell (kpt) Argo CD automated reconciliation
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:47Key tools overview
- 2:49Kubernetes adoption
- 6:00Cluster API benefits
- 8:04Cluster API architecture
- 14:42Bare metal provisioning
- 17:29Cluster API + Tinkerbell
- 20:15GitOps automation
- 22:00Demo setup
- 31:27Conclusion & Q&A
related talks
38mBare-Metal Chronicles: Tinkerbell, Cluster API & GitOps
35mBare-Metal Chronicles: Intertwinement Of Tinkerbell, Cluster API And GitOps
14mTalk Deep Dive
28mTaking Bare Metal to the Clouds with Tinkerbell
32mGitOps, an Elegant Tool for Hybrid Cloud Kubernetes
26mGitOps Me Some of That! Managing Hundreds of Clusters with Argo CD
01h 38mScaling Multi-cluster Management with Argo CD and Application Sets
36mBare metal Kubernetes on mixed x64 and ARM64
