The Atomic Host platform is now replaced by CoreOS. Users of Atomic Host are encouraged to join the CoreOS community on the Fedora CoreOS communication channels.
The documentation contained below and throughout this site has been retained for historical purposes, but can no longer be guaranteed to be accurate.
Since Fedora 27 Atomic recommends installing Kubernetes as a system container, what follows is a refresher on them featuring etcd.
System containers exist as a way to provide containerized services to a host before traditional container runtimes are ready. System containers do this by utilizing a runc and systemd units and do not deviate from the OCI standards. Let’s look at how someone can use a system containers to install the ever popular etcd today on Fedora 27 Atomic Host!
We are proud to announce that multiple architectures are now supported with Fedora 27 Atomic Host release! Now, along with x86_64 architecture, Atomic Host is also available on 64 bit ARM (AArch64) and PowerPC Little Endian (ppc64le). Both aarch64 and ppc64le architectures will receive Atomic OSTree updates in the same way x86_64 does.
Starting with Fedora 27 Atomic Host, the RPMs for Kubernetes, Flannel and Etcd are no longer included in the host’s image, but are installable instead either as system containers or via package layering.
This week we put out the first release of Fedora 27 Atomic Host. Some quick notes:
In Fedora 27 Atomic Host we removed kubernetes from the base OSTree. We will have a post tomorrow about the upgrade steps for Kubernetes users.
For Fedora 27 we are currently sticking with the non-unified repo approach as opposed to a unified repo. TL;DR nothing is changing for now but we expect to implement a unified repo as described here during the F27 release cycle.
For today we’ll talk about updating an existing Fedora 26 Atomic Host system to Fedora 27. We’ll cover preparing the system for upgrade and performing the upgrade.
Fedora 27 Atomic Host is now available. Highlights of this version include multi-architecture support, containerized Kubernetes, a single OverlayFS volume by default, and new OSTree layering capabilities.
Over the next week or so, we will have additional posts on each of these features, giving technical details and use-cases. But today, for the release, we’ll have quick summary of the major changes.