How RHOSO versions map to OpenStack Operators and OpenStackVersion CRs

Map versions of Red Hat OpenStack Services on OpenShift (RHOSO) to OpenStack Operator versions and OpenStackVersion Custom Resources (CRs) to plan for minor updates or troubleshoot technical issues in your RHOSO environment.

Version summaries

The following summaries describe the difference between the RHOSO version, OpenStack Operator version, and OpenStackVersion numbers.

RHOSO version

Product releases of Red Hat OpenStack Services on OpenShift, including bug fix releases and feature releases.

OpenStack Operator version

Central point for managing the OpenStack control plane by using CRs to configure other operators for OpenStack services. You install the version of the openstack-operator from the OperatorHub Marketplace that maps to the version of RHOSO you want to use.

OpenStackVersion

The long number, for example, 18.0.9-20250602.2, that administrators see as the availableVersion or targetVersion in the OpenStackVersion CR in an openstack namespace. During a minor update, you set the value of the targetVersionfield in the OpenStackVersion CR to match the value of the availableVersion field. These OpenStackVersion numbers map to available and target openstack-operator versions, for example, 1.0.11.

Checking versions

You can check which version of the OpenStack Operator is deployed and which version is available for a minor update. The command output shows the OpenStack Operator target and available versions. Use the target version to determine which version of RHOSO is installed:

$ oc get openstackversion
NAME              TARGET VERSION   AVAILABLE VERSION    DEPLOYED VERSION
openstack         1.0.0            1.0.1                1.0.0

Version map

Additional resources

• For information on supported OpenShift Container Platform versions for RHOSO, see OpenStack Product Life Cycle
• For information about OpenShift Operator Life Cycles, see OpenShift Operator Life Cycles.