Expand OpenShift lifecycle to 24 months for multi-arch (ARM, Z, and Power)

BU Priority Overview

Expand OpenShift lifecycle for ARM, Z, and Power to 24 months by adding a 6 month Extended Update Support (EUS) phase equivalent to that provided in 4.12 for x86

Goals

Provide an equivalent lifecycle for customers consuming OpenShift on ARM, Z, and Power to that offered in x86. Both in homogeneous and heterogeneous clusters.

State of the Business

OpenShift on IBM Power and IBM zSystems is a small, but growing, area of OpenShift adoption that is important to many key customers as well as our multi-architecture strategy. They have been classed for some time now as "first class" architectures which sets expectations around not only features and releases but also support. When you add in Arm support, a key initiative for Red Hat, aligning lifecycles become very important to adoption, otherwise the architectures will be seen (and treated) as second class citizens. With the addition of support for mixed architecture clusters this alignment becomes even more important as if it differs by architecture the customers could find themselves in the situation where part of their cluster is supported and part isn't. 

Execution Plans

Plan to add EUS phase on ARM, Z, and Power in 4.14.

dgilmore.fedora  to expand.

 
Acceptance criteria

• OCP 4.14 lifecycle of 24 months includes ARM, Z, Power (in addition to x86) (but not applicable to OCP 4.12)
• https://access.redhat.com/support/policy/updates/openshift updated