Goal

tl;dr; I am requesting permission and support for backporting the work in CNV-50822 and the corresponding UI changes to 4.20.z (work on this to start after CNV-4.21 GA).

MTC is planning to sunset on Dec 31, 2026.  We need to discuss the impact of this on our Storage Class Migration feature across various OCP versions.

• OCP-4.18 and earlier - no impact because storage class migration is not supported yet
• OCP-4.19 - no impact because this version of OCP will be EOL
• OCP-4.20 - See below
• OCP-4.21 - no impact because we will support storage class migration natively

OCP 4.20 does not EOL until the end of 2028.  This creates a 2 year gap where MTC is gone but customers may still use OCP-4.20.

We have two options: maintain MTC ourselves until OCP-4.20 EOL or backport the native support to CNV-4.20.z.  I prefer to backport even though it breaks our usual rule of not introducing new things in a z-stream release.  From a customer perspective this feature is already GA and it must keep working.  Backporting the new code focuses our engineers on the present and future rather that on throw-away maintenance activities.  Customers will need to migrate to the new APIs eventually.  If they are using the UI the only change they will notice is that they no longer need to install MTC (no change if they had it installed already as we will simply stop using it).

The backport work can wait until after the feature is delivered into CNV-4.21.

User Stories

• As a VM owner I want to continue using the GA feature storage class migration on OCP 4.20 for the duration of its lifespan.  I don't want to lose access to this feature when MTC sunsets EOY 26.

Non-Requirements

• List of things not included in this epic, to alleviate any doubt raised during the grooming process.

Notes

• Any additional details or decisions made/needed