Epic Goal

• Upgrade to the latest OADP version as a dependency for MTC. Depending on when this release ships, this will be OADP 1.2.x or 1.3.x.

Why is this important?

• In order for us to continue to support 4->4 migrations, it's important that MTC can be installed with newer instances of OADP.

Scenarios

1. A customer who has installed OADP 1.2 (or latest), also wants to install MTC. 

Acceptance Criteria

• Release Technical Enablement - Provide necessary release enablement details and documents.
• Testing is done to verify OADP and MTC both work with latest version installed on OCP 4 only.

Dependencies (internal and external)

1. OADP

Previous Work (Optional):

1. …

Open questions::

1. How do we continue to support multiple release steams for MTC moving forward?
2. How do we continue to support 3->4 migrations?
   1. This new version of MTC will only be installed on clusters using it for 4->4 migrations.

Done Checklist

• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>