This ticket tracks the necessary File-Based Catalog (FBC) modifications to re-enable Migration Toolkit for Containers (MTC) support for OpenShift Container Platform (OCP) versions 4.12 and 4.13.

Following the versioning divergence caused by the OCP 4.18 release cycle, we are realigning the 1.8.z stream. The goal is to provide a clean upgrade path to v1.8.14, which will serve as the new baseline for all supported OCP versions.

Key Changes in the FBC

To ensure OLM correctly resolves the upgrade path, the mtc-operator.v1.8.14 entry will be updated with the following logic:

• Replaces: Sets mtc-operator.v1.8.0 as the base replacement to ensure broad compatibility.

• Skips: Explicitly lists versions v1.8.0 through v1.8.8 to prevent OLM from attempting intermediate hops that may no longer be available or valid in the 4.12/4.13 catalogs.

• SkipRange: Implements skipRange: ">=0.0.0 <1.8.14". This forces a direct "jump" to 1.8.14 for any user currently on an older 1.8.z version, bypassing the broken 1.8.9–1.8.13 gap.

Intended Upgrade Paths

This configuration supports two primary personas:

1. Stable OCP 4.12/4.13 Users: Will upgrade directly from 1.8.8 $\rightarrow$ 1.8.14.

1. Impacted OCP 4.18 Users: Will upgrade from their current state (e.g., 1.8.12) $\rightarrow$ 1.8.14.

1. Forward Path: Post-1.8.14, the graph will return to a standard linear progression (1.8.14 $\rightarrow$ 1.8.15 $\rightarrow$ 1.8.16).

Release Notes

Release Note

Overview

MTC v1.8.14 is now available and restores full support for OpenShift Container Platform (OCP) versions 4.12 and 4.13. This release realigns the MTC upgrade path across all supported OpenShift versions, ensuring a stable foundation for future updates.

Important: Upgrade Path Information

To streamline the transition and resolve previous versioning conflicts, MTC 1.8.14 introduces a direct upgrade path.

• For OCP 4.12 and 4.13 users: If you are currently on the latest available version (typically 1.8.8), you will see a direct update to 1.8.14.

• For OCP 4.18 users (and affected clusters): If your cluster was impacted by the recent versioning divergence (running versions such as 1.8.12), you will be prompted to upgrade directly to 1.8.14.

Note: This "jump" is intentional. By upgrading to 1.8.14, your cluster will be aligned with the new standard maintenance stream. All future updates (e.g., 1.8.15 and beyond) will follow a standard linear progression.

What’s New in 1.8.14

• Restored Compatibility: Full validation for MTC operations on OCP 4.12 and 4.13 environments.

• Streamlined Catalog: Optimized Operator Lifecycle Manager (OLM) logic to ensure smooth transitions from legacy 1.8.x versions.

• Stability Fixes: Includes all critical patches and performance improvements rolled up from the 1.8.9–1.8.13 development cycle.

Recommended Action

Users on OCP 4.12 and 4.13 are encouraged to upgrade to MTC 1.8.14 at their earliest convenience to ensure continued support and access to future security patches.