Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
machine-config-operator
This operator is an integral part of the operator-focused OpenShift 4 platform. It manages and applies configuration and updates of the base operating system and container runtime; essentially everything between the kernel and kubelet.
The approach here is a "fusion" of code from the original CoreOS Tectonic as well as some components of Red Hat Enterprise Linux Atomic Host, as well as some fundamentally new design.
The MCO (for short) interacts closely with both the installer as well as Red Hat CoreOS. See also the machine-api-operator which handles provisioning of new machines - once the machine-api-operator provisions a machine (with a "pristine" base Red hat CoreOS), the MCO will take care of configuring it.
One way to view the MCO is to treat the operating system itself as "just another
Kubernetes component" that you can inspect and manage with oc.
The MCO uses CoreOS Ignition as a configuration format. Operating system updates use rpm-ostree.
Sub-components and design
This operator is split into 4 components; the above covers the operator. Here are links to design docs for the sub-components:
Interacting with the MCO
View operator status:
oc describe clusteroperator/machine-config-operator
Inspect the status of the machineconfigpool objects which track upgrades:
oc describe machineconfigpool
(More to come)
Developing the MCO
See HACKING.md.