is not config management Static configuration Written in Go - self-contained; community; CoreOS fit Configuration specification and JSON How is it different than CloudInit?
depend on the network Ignition runs early configures networkd with the unit interface… ...and services with systemd units, then pivots “Let systemd do it.” How is it different than CloudInit (2)?
management Atomic provisioning (“Don’t reconfigure. Reprovision.”) Static config - no “2-stage cloud-config” invoking a sh script Same semantics across environments Why use Ignition?
networkd units - services and networks - configure etcd, kubelet Users and groups - ssh and keys Remote configs - HTTP, validate a sha for the target What can Ignition do?