Bare-Metal Chronicles: Intertwinement Of Tinkerbell, Cluster API And GitOps
summary
Shows a concrete stack: Cluster API + a kpt (Cluster API provider for Tinkerbell) provider, Tinkerbell hardware templates/workflows, Helm for templating, and Argo CD sync for GitOps. Cites that ~88% of orgs run >6 clusters and ~52% still need bare metal. Demo uses a management cluster to commit a Helm value change, Argo CD detects it, Cluster API provisions three additional control/data machines (simulated on AWS) and nodes come up ready — a working, repeatable bare‑metal provisioning loop.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 1:00Cluster API overview
- 5:01Cluster API mechanics
- 13:53Introduction to Tinkerbell
- 16:54CAPI and Tinkerbell synergy
- 19:37GitOps integration
- 22:58Live demo and scaling
- 31:11Summary and conclusion
related talks
33mBare-Metal Chronicles: Intertwinement of Tinkerbell, Cluster API and GitOps
38mBare-Metal Chronicles: Tinkerbell, Cluster API & GitOps
14mTalk Deep Dive
28mTaking Bare Metal to the Clouds with Tinkerbell
36mBare metal Kubernetes on mixed x64 and ARM64
32mGitOps, an Elegant Tool for Hybrid Cloud Kubernetes
24mImage-Based Bare-Metal Provisioning With Metal3.io, Cluster API and…
29mTales from the Branches: GitOps in the Real World