As of MTC version 1.8.13, the operator now utilizes the olm.maxOpenShiftVersion property. Since OpenShift 4.20 is the final supported version for MTC, this technical constraint has been implemented to explicitly block the cluster from upgrading to OCP 4.21 or higher while the MTC operator is present.

Current Behavior: The cluster upgrade path to OCP 4.21+ is restricted by OLM because MTC 1.8.13 signals it is incompatible with versions beyond 4.20.

Desired Outcome: We need to ensure this is documented (e.g., in Release Notes or Troubleshooting guides) so users understand that:

1. The upgrade blockage is intentional.

1. To proceed with an OCP upgrade to 4.21+, MTC must first be uninstalled.

Technical Details

• MTC Version: 1.8.13

• Property: olm.maxOpenShiftVersion: "4.20"

• Impact: Prevents OCP Z-stream/Minor upgrades to 4.21 and above.

Acceptance Criteria

• [ ] Update the Release Notes for MTC 1.8.13 to include this constraint.

• [ ] Update Installation/Upgrade guides to mention that MTC must be removed before upgrading the cluster to OCP 4.21+.

Addendum

• If an admin is trying to upgrade their cluster at 2:00 AM and it’s blocked, they might panic. Mentioning that this is a "guardrail" rather than a "bug" helps lower the stress level.

• It might be worth adding a note in the ticket if there's a specific reason MTC is EOL-ing at 4.20 (e.g., transitioning to a new tool), just for internal context.