Unlocking Cloud-Native Efficiency: A Journey with Flatcar
summary
Flatcar is a minimal, read‑only container OS built from Gentoo ebuilds with A/B partitioning for atomic updates and system extensions layered on top to let operators change runtime behavior without mutating the base image. Images are rebuilt from scratch and validated across 100+ test scenarios, an image builder and bakery produce deployable artifacts, and a Cluster API integration lets Kubernetes roll forward by restarting nodes. Demonstrated on OpenStack, targeted for Azure, and now in CNCF incubation.
AI-written summary · about
chapters (13)
- 0:00Introduction to Flatcar
- 1:42What is Flatcar
- 3:33Flatcar's heritage and design
- 5:00Advantages of declarative approach
- 6:47Composable Linux with systemd extensions
- 8:58Flatcar configuration and usage
- 10:49Cluster API and Kubernetes integration
- 13:18Introducing Container Karma
- 16:09Flatcar joining CNCF
- 17:33Container OS working group
- 18:38CNCF TAG Runtime involvement
- 20:05Ways to contribute to CNCF
- 21:53Q&A session
related talks
23mNomad + Flatcar: A Harmonious Marriage of Lightweights
27mFull Stack Cloud Native Packaging – An Intro to CNAB - Ben Griffin & Clarence Bakirtzidis, Microsoft
33mCNCF TAG-Runtime: Cloud Native Open...
01h 00mBuilding Cloud-Native Applications
32mCloud Native Progressive Delivery
55mFrom my Machine to the Cloud with Cloud-Native Tools
23mMaking Cloud Native Computing Universal and Sustainable
48mIntro to Cloud Native Buildpacks