• We have had quite a few cases where customer have upgraded their ACM from 2.4 to 2.6 and that lead us into issues.
• This can be avoided if we restrict users from selecting the latest version in the OCP UI and only provide option to upgrade the operator to the next major version.
• We do have mentioned in the doc that upgraded jumping major versions is not supported, but based on the issues that we had, we can assume that the customer does not look for this information in the docs as they see that the option to jump versions is available in the ocp UI.
• We could restrict users from selecting the Subscription channel other than the next major release. Allowing to select any version channel is useless because I am assuming that we do not support downgrades?

ACM Epic Done Checklist

See presentation and details.

Update with "Y" if Epic meets the requirement, "N" if it does not,  or "N/A" if not applicable.

• _ FIPS Readiness
• _ Works in Disconnected
• _ Global Proxy Support
• _ Installable to Infrastructure Nodes
• _ No impacts to Performance and Scalability
• _ Backup and Restorable