Red Hat Enterprise Linux CoreOS 10 is coming to Red Hat OpenShift

Every OpenShift admin knows the calculus. A new Red Hat Enterprise Linux CoreOS ships with capabilities you want: better hardware support, updated crypto policies, kernel improvements. But adopting it has always meant adopting it everywhere. Your hardware certifications don't transfer automatically. Your internal validation pipeline needs another quarter. Your change advisory board wants a rollback plan for something that hasn't historically rolled back gracefully.

The result is that teams delay platform upgrades to avoid the OS migration, missing capabilities they actually need. The OS upgrade has been a cliff, not a ramp.

With Red Hat Enterprise Linux 10, we’re changing that.

To get there, we’ve introduced tech preview of Red Hat Enterprise Linux CoreOS 10 in Red Hat OpenShift 4.22 and, in a future release of Red Hat OpenShift, clusters will be able to run different Red Hat Enterprise Linux CoreOS streams at the same time. Red Hat Enterprise Linux CoreOS 9 and Red Hat Enterprise Linux CoreOS 10 nodes coexist in the same cluster as a supported transitional operating model so that upgrading feels no more disruptive than upgrading any other minor Red Hat OpenShift release. Migration happens at your pace, one MachineConfigPool at a time. 

Let's talk about what multi-OS stream support means for your clusters, what Red Hat Enterprise Linux CoreOS 10 delivers today, and where the platform is heading next.

Multi-OS stream: How it works

Introducing OSStreams, a new cluster-level API resource that lets the Machine Config Operator manage multiple Red Hat Enterprise Linux CoreOS versions in the same cluster. 

If you're doing a fresh install, you get Red Hat Enterprise Linux CoreOS 10 by default. There's a documented path to install with Red Hat Enterprise Linux CoreOS 9 if your environment requires it. Maybe your hardware certifications are tied to Red Hat Enterprise Linux 9 or your internal validation cycle hasn't cleared Red Hat Enterprise Linux 10 yet. Either way, it's a supported choice, not a workaround.

If you're upgrading from Red Hat OpenShift 4.22, your nodes stay on Red Hat Enterprise Linux CoreOS 9. No forced OS migration on day 1. You upgrade the platform and keep the node OS you've already validated. When you're ready to move nodes to Red Hat Enterprise Linux CoreOS 10, you have time to do it on your schedule.

Migration is one MachineConfigPool-at-a-time. Create a custom MachineConfigPool, put even a single node in it, point it at the Red Hat Enterprise Linux CoreOS 10 stream, and validate your workloads. If everything looks good, move forward. If something doesn't, the node goes back. This is the same drain/cordon/reboot cycle the MachineConfigPool already uses for every config change. No new rollback mechanism, no new risk model.

Red Hat Enterprise Linux CoreOS 9 nodes continue receiving support alongside Red Hat Enterprise Linux CoreOS 10. That gives you a long runway to migrate to Red Hat Enterprise Linux CoreOS 10 rather than being forced into a short deadline.

The OS upgrade becomes a migration. No cliff. No weekend cutover. Gradual, validated, reversible.

Why Red Hat Enterprise Linux CoreOS 10 is worth the move

Red Hat Enterprise Linux CoreOS 10 inherits the Red Hat Enterprise Linux 10 kernel, which means newer hardware enablement across GPUs, NICs, NVMe, and CXL devices. If you're running newer server hardware or planning to, Red Hat Enterprise Linux CoreOS 10 is where the driver support lands first. Scheduler and memory management improvements mean better latency behavior and more efficient page reclaim under pressure, which matters for dense, high-utilization nodes.

Red Hat Enterprise Linux CoreOS 10 is built on the same Red Hat Enterprise Linux 10 foundation that enables sealed image mode, a technology that provides continuous cryptographic integrity verification using composers and fs-verity. Not just boot-time verification, but every file read cryptographically validated. Customer-controlled signing keys. A trust chain from firmware to filesystem. It also enables post-quantum cryptography from Red Hat Enterprise Linux, so you can begin testing NIST-approved, quantum-resistant algorithms with your organization to start protecting your data and preparing to meet future regulatory requirements.

Start planning your migration

Red Hat Enterprise Linux CoreOS 10 is available in tech preview in Red Hat OpenShift 4.22. 

When you're ready to test Red Hat Enterprise Linux CoreOS 10: On a test cluster, create a custom MachineConfigPool with a single node. Point it at the Red Hat Enterprise Linux CoreOS 10 stream. Run your validation workloads against it. This is low-risk by design: one node, one pool, fully reversible.

When you're confident: Once the feature is GA and you’re happy with your testing, expand pool by pool. Move production-critical workloads last.

If you use on-cluster layering: MachineOSConfigs are MCP-scoped, so make sure yours accounts for any OS-sensitive build steps when migrating pools to Red Hat Enterprise Linux CoreOS 10. Test your layered images against both Red Hat Enterprise Linux CoreOS 9 and Red Hat Enterprise Linux CoreOS 10 base images before expanding migration.

Extended transition timeline. Red Hat Enterprise Linux CoreOS 9 remains fully supported. You migrate when the value of Red Hat Enterprise Linux CoreOS 10 outweighs the cost of validation for your specific environment. For some teams, that's day 1. For others, it's next quarter. Both are fine.

Multi-OS stream support gives you the flexibility to modernize the OS at your own pace. Red Hat Enterprise Linux CoreOS 10 means the destination is genuinely worth reaching. You no longer have to choose between upgrading your platform and keeping your nodes on proven ground.

The upgrade cliff is gone. Welcome to the ramp. Get started with Red Hat Enterprise Linux CoreOS 10 now, available in Tech Preview with Red Hat OpenShift 4.22