CoreOS supports its own version of cloud-init, with added support for the CoreOS environment, and without everything else incompatible with its environment, so we can boot a fully configured system and cluster.
We'll take a look at the CoreOS specificities, as we can refer to earlier tips on how to manage users, files, authorized SSH keys, and other standard cloud-init directives. At the end of this part, you'll know how to configure the etcd key value store, the fleet cluster manager, the flannel overlay network, control the update mechanism, and ensure systemd units are started as early as possible.
Note
CoreOS proposes a very useful cloud-config file validator at https://coreos.com/validate/. It's super useful when we're not sure if a directive is supported or not in the distribution.
To step through this recipe, you will need:
Access to a cloud-config enabled infrastructure
