Need to be able to specify an older version of OCP when installing on ARO

[wilfredjamison]

Some products, such as Cloud Paks from IBM, that run on top of OpenShift are not necessarily in syched with the latest version of OpenShift. They may be 1 minor version behind because they cannot test the new OCP version ahead of time before it gets released.

Having said that, this introduces a major problem when a customer wants to use a Cloud Pak product on ARO. The ability to specify an older version is a major need in this use case, or this will cause a customer to drop ARO as an option since ARO is not the only way that the Cloud Pak products can be deployed. Microsoft may be losing revenues if you don't support this scenario.

[kris234]

When we deploy a solution on the current version of OpenShift available on ARO, we need to be able to stay on this version of OpenShift until the solution supports a future version of OpenShift. Is this scenario supported on ARO where the original version of OpenShift on which we deployed is now a minor version.

[PKirkby]

This is really an issue for IBM Engineering Requirements Quality Assistant as well. This has caused major pain where the test cluster deployed was 4.7 and doing the production deployment we received a 4.8 cluster and could no longer install the software. Imagine if this was a disaster recovery scenario.

Please note that the Microsoft.RedHatOpenShift/openshiftClusters ARM template actually specifies a version parameter - I had to contact support to get information that the only valid value is latest version. (at the time of writing 4.8)

[TiloGit]

see #208