CoreOS has a project called ignition that hooks into early boot processes in the initramfs (i.e. before and after the root filesystem is mounted) and allows for configuration of the system. This is an alternative to cloud-init, that is focused on specific tasks. Let's investigate this for Fedora and Atomic Host.
Metadata Update from @dustymabe: - Issue tagged with: meeting
Good progress here on the Proof of Concept level. More soon.
This makes me very happy. Looking forward to the update!
Metadata Update from @dustymabe: - Issue untagged with: meeting
Metadata Update from @miabbott: - Issue assigned to dustymabe
https://www.redhat.com/archives/anaconda-devel-list/2018-April/msg00005.html
What was the outcome of this?
Asking because of https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/69#issuecomment-469319484
Colin answered upstream: https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/69#issuecomment-469391931
Colin Walters, CoreOS engineer at Red Hat, Inc. (@walters) wrote:
Fedora CoreOS will succeed Fedora Atomic Host and it will use Ignition.
Log in to comment on this ticket.