Supported migration paths from Red Hat OpenShift AI 2.25.x to 3.x
The Red Hat OpenShift AI 3.0 release introduced significant technology and component changes, making a direct upgrade from version 2.25 technically complex. Migration from 2.25.x to 3.x is supported only to specific 3.x releases, using the rhai-cli assessment tooling and a documented migration guide.
IMPORTANT: OpenShift AI 2.25.x customers must complete the migration assessment described in the migration guide for your chosen target release before attempting any upgrade.
Supported migration targets
| Target release | Migration from 2.25.x supported? | Minimum source version |
|---|---|---|
| 3.0 / 3.1 / 3.2 | No | — |
| 3.3.2 and later 3.3.z | Yes | 2.25.4 |
| 3.4 | No | — |
| 3.5 | Yes | 2.25.10 |
There are currently two supported migration targets: 3.3.2 and 3.5. Each has its own dedicated migration guide; they are parallel editions, not sequential steps. You do not migrate to 3.3 first in order to reach 3.5.
- 3.3.2 was the first 3.x release to support migration from 2.25.x. See Assess and plan for migration from OpenShift AI 2.25.4 (and later) to 3.3 (latest).
- 3.4 has no migration path from 2.25.x. There is no 3.4 migration guide, and the 3.4 release notes contain no installation/upgrade path chapter. 2.25.x customers must target 3.3.2 or 3.5.
- 3.5 supports migration from 2.25.10 and later. See Assess and plan for migration from OpenShift AI 2.25.10 (and later) to 3.5.
Choosing a target
Red Hat OpenShift AI 3.5 is an Extended Update Support (EUS) release. OpenShift AI 3.5 enters its EUS phase when Full Support ends on March 27, 2027, and the eus-3.5 update channel is available after migration. For customers who cannot absorb frequent upgrades, 3.5 is the recommended migration target.
OpenShift AI 3.3 is not an EUS release. Customers migrating to 3.3 should plan to continue upgrading within the 3.x line.
For lifecycle dates and support phase windows, see the Red Hat OpenShift AI Self-Managed Life Cycle Knowledgebase article.
Update channels
Migration to 3.5 is triggered by the support-required-upgrade-3.5 channel. After the upgrade completes, move off this channel and select a supported channel for your environment — stable-3.5, stable-3.x, or eus-3.5.
OpenShift AI 3.3 is the last release available under the fast channel. If you migrated to 3.3, switch from fast to stable-3.x after the upgrade.
For channel definitions, release frequency, and the support window associated with each channel, see Understanding update channels in Installing and uninstalling OpenShift AI Self-Managed.
For existing 3.x customers (not migrating from 2.x)
- New installations: install on a cluster running OpenShift Container Platform 4.19.9 or later and select the
stable-3.xchannel. - Upgrades within 3.x: sequential upgrades between 3.x releases are fully supported and do not require the migration assessment process.
Lifecycle
OpenShift AI 2.25 is a stable and EUS release and will continue to be supported for an extended period per the defined lifecycle. In the 3.x line, 3.5 is the EUS release.
See the Red Hat OpenShift AI Self-Managed Life Cycle Knowledgebase article for the full support phase windows and end dates.
References
- Assess and plan for migration from OpenShift AI 2.25.4 (and later) to 3.3 (latest)
- Assess and plan for migration from OpenShift AI 2.25.10 (and later) to 3.5
- Red Hat OpenShift AI Self-Managed 3.3 Release Notes
- Red Hat OpenShift AI Self-Managed 3.5 Release Notes
- Red Hat OpenShift AI: Supported Configurations for 3.x (KCS 7133798)
- Red Hat OpenShift AI Self-Managed Life Cycle
Comments