Immutable Infrastructure with Flatcar Container Linux
summary
Describes using Flatcar Container Linux (a CoreOS fork) together with Terraform, Ignition and Ansible to implement immutable-infrastructure workflows. Covers Flatcar’s A/B update partitions and Ignition’s declarative first-boot config, discusses trade-offs of using Ansible instead of Ignition (accepting possible configuration drift), and presents a proof-of-concept approach to re-run Ignition or selectively clear filesystem parts to apply configuration changes without full reprovisioning.
AI-written summary · about
related talks
47mImmutable Infrastructure GitHub + Terraform + Packer
39mAutomating Immutable Infrastructure With Packer & Terraform
33mThe "what" and "why" of Flatcar Linux, a friendly fork of Container Linux
26mIs Immutable Infrastructure Feasible?
27mApplication-Driven Infrastructure
01h 02mTools and Techniques for Infrastructure as Code
32mInfrastructure Automation (anti) patterns
36mBuild infrastructure as a code (IaC) using test-later...