Fedora CoreOS

Fedora CoreOS
Name	Fedora CoreOS
Developer	Red Hat
Family	Linux (Unix-like)
Working state	Active
Source model	Open source
Initial release	2018
Latest release	Rolling
Kernel type	Monolithic (Linux)
Marketing target	Container hosts, cloud
License	GPL, LGPL, MIT, others

Fedora CoreOS is an automated, minimal, container-focused operating system designed for running containerized workloads at scale. It combines technologies from Project Atomic, Container Linux (formerly CoreOS), and the Fedora Project to provide an immutable, update-first foundation for orchestrators like Kubernetes, OpenShift, and Docker Swarm. The distribution emphasizes automatic updates, small image footprints, and integration with cloud platforms such as Amazon Web Services, Google Cloud Platform, and Microsoft Azure.

Overview

Fedora CoreOS targets production deployments requiring container orchestration and immutable infrastructure patterns encountered in cloud-native computing, DevOps, and site reliability engineering teams at organizations like Netflix, Airbnb, GitHub, and Spotify. It builds on the Linux kernel and packages from Fedora while adopting update and provisioning models popularized by CoreOS, Inc. and the CoreOS Container Linux lineage. The OS is designed to work with orchestration projects like Kubernetes and management tools such as Ansible, Terraform, Puppet, and Chef on platforms including OpenStack and VMware vSphere.

History and Development

Fedora CoreOS emerged after Red Hat's acquisition of CoreOS, Inc. and the subsequent sunsetting of Container Linux. Development involved contributors from Red Hat, the Fedora Project, and upstream projects like Ignition and rpm-ostree. Early milestones included upstream proposals at FOSDEM and collaboration with maintainers of atomic-host technologies. The project tracks innovations from Fedora Workstation and Fedora Server while aligning with enterprise offerings such as Red Hat Enterprise Linux and Red Hat OpenShift. Governance and roadmap discussions have occurred at venues including KubeCon and the Open Source Summit.

Architecture and Components

The architecture centers on an immutable root filesystem managed by rpm-ostree and a user-data provisioning mechanism enabled by Ignition. Container runtimes such as CRI-O and containerd provide OCI-compatible execution for images built with Buildah and Podman. System services are orchestrated via systemd units with networking handled by integrations like NetworkManager for desktops and CNI plugins used in Kubernetes clusters. Bootstrapping uses cloud-init analogues and integrates with cloud provider metadata services from Amazon EC2, Google Compute Engine, and Microsoft Azure Virtual Machines. Logging and observability often rely on stacks incorporating Prometheus, Grafana, Fluentd, and Elasticsearch.

Installation and Update Mechanisms

Deployments can be provisioned with platform-specific images for providers such as AWS Marketplace, Google Cloud Marketplace, and Microsoft Azure Marketplace, or via ISO images on hypervisors like KVM, Xen, and VMware ESXi. The update model leverages transactional atomic upgrades through rpm-ostree with automatic reboots optionally managed by integration with orchestration layers like Kubernetes Node lifecycle controllers. Configuration is applied at first boot via Ignition files and can be layered with container-focused provisioning tools such as Ignition Config Transpiler workflows and configuration management through Terraform modules.

Security Features

Security is implemented via an immutable base, reproducible builds, and automatic, atomic updates to reduce drift; it benefits from efforts in SELinux enforcement and kernel hardening techniques backported from Red Hat Enterprise Linux. Container isolation is provided by Linux primitives including namespaces and cgroups, and runtime security integrates with projects like seccomp and AppArmor where applicable. Image signing and verification workflows utilize OpenPGP and package signing approaches similar to those in RPM ecosystems, while integrations with identity and access management solutions such as OAuth 2.0 providers and LDAP systems support multi-tenant environments.

Use Cases and Adoption

Common use cases include hosting microservices in Kubernetes clusters at enterprises and startups such as Goldman Sachs, Spotify, and Salesforce for CI/CD runners, edge nodes, and ephemeral compute instances. Organizations adopt Fedora CoreOS for immutable infrastructure initiatives, blue/green deployment strategies, and secure, minimal hosts for platform services like Istio and Linkerd. Cloud providers and managed service vendors incorporate the OS into offerings alongside orchestration services from Amazon EKS, Google GKE, Azure AKS, and Red Hat OpenShift.

Community and Governance

The project is governed through collaboration between the Fedora Project community, contributors from Red Hat, and external maintainers. Governance and roadmap items are discussed in forums like Fedora Discussion, issue trackers on platforms such as GitLab, and at conferences including KubeCon and FOSDEM. Contributions follow contributor agreements and code review practices modeled after those in Fedora and Red Hat upstream processes, with packages and changes coordinated via the rpm-ostree and Ignition repositories.

Category:Linux distributions Category:Red Hat software