OpenShift OS customization as bootable container!
summary
OpenShift 4.12 switches OS updates to a bootable OCI image so admins can layer packages via a Containerfile and push a custom image, then point a machineconfig override at the image SHA. Demo builds with rpm-ostree tooling and standard container tooling, applies via MCO which cordons and drains nodes and upgraded a kernel from 5.14.0.5 to 5.14.0.325 on a worker successfully. Off‑cluster builds land in 4.13, in‑cluster builds and RT kernel/extension support remain work in progress.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:51Background
- 2:39Machine Config Operator (MCO)
- 3:51Limitations
- 6:46OCP CoreOS Layering
- 7:42Bootable Container
- 8:44Comparing OS image content
- 11:01Example (hotfix and package layering)
- 22:41Where we are
- 23:13Off-Cluster builds
- 24:13Things to remember!
- 25:13What's next
- 26:34Resources
related talks
45mRed Hat CoreOS and OpenShift v4
33mBootable Containers: An entire OS as a Containerfile
44mWhat is Red Hat CoreOS?
24mCoreOS Demystified – The Specialized OS Powering OpenShift and Containers
19mOpenShift in your own backyard
17mOpenshift 4 0 on Red Hat CoreOS & Enterprise Linux 8
23mCodeReady Containers: Run OpenShift 4 locally
10mKubernetes: Enabling Edge Workloads