OpenShift 5 brings hosted control planes and agentic troubleshooting to ROSA

Red Hat says OpenShift 5 is now available on Red Hat OpenShift Service on AWS (ROSA) through the hosted control plane architecture, bringing the new platform generation to customers of its jointly managed AWS service. The announcement matters less as another OpenShift 5 feature list than as a statement about where the operational boundary moves for managed clusters. Red Hat says the control plane runs in a Red Hat-owned AWS account, while customers pay for the worker-node compute, networking and storage in their own environment.

A different managed-cluster shape

The hosted-control-plane model decouples control-plane infrastructure from customer worker capacity. Red Hat says that can shorten cluster provisioning, reduce the infrastructure charged to the customer account and limit accidental changes to control-plane resources. AWS managed policies define the service’s security profile under least-privilege scopes, according to the same announcement.

That is a concrete deployment consequence for ROSA users evaluating OpenShift 5. The new release is not only a software update to an existing classic cluster shape; Red Hat points customers to a separate learning path for migrating applications from classic ROSA clusters to hosted control planes.

Troubleshooting moves into the console

OpenShift Lightspeed’s agentic troubleshooting is also available in the ROSA console with OpenShift 5. Red Hat says its answers are grounded in official OpenShift and ROSA documentation and can investigate prompts about failed deployments or high CPU use before proposing remediation steps.

The useful boundary is in the wording: this is a troubleshooting and recommendation surface, not a claim that the service will silently repair production workloads. Platform teams should still treat generated steps as operational advice that needs review against their own change controls.

Lifecycle policy follows the platform

ROSA also inherits OpenShift 5’s longer support model. Red Hat extends standard support from 18 to 24 months for each release and plans an Extended Life Cycle option beginning with 5.2. Every third designated release can receive three additional years, for as much as five years of total support. Automated preflight checks are intended to flag API compatibility and update risk before an upgrade.

For ROSA operators, the decision is therefore bundled: adopt OpenShift 5 capabilities, move toward hosted control planes and plan against the new lifecycle cadence. The managed service removes some infrastructure ownership, but it does not remove the need to test application compatibility or govern AI-assisted remediation.