We need to do investigation to determine what UI changes we should consider for upgrading between 4.6 -> 4.10 Extended Update Support (EUS) releases. For background on this initiative, see

EUS to EUS Focus Area Discussion: https://docs.google.com/document/d/17I1Wd7-R1wRxmboyv1jUFHFkqQcBTorJccdGi1ZqjQE/edit?usp=sharing

EUS Feature: https://issues.redhat.com/browse/OCPPLAN-5484

• Is the EUS -> EUS upgrade user experience different than manually upgrading to each separate release?
• Should we show status differently in the UI during an EUS -> EUS upgrade?
• Do we need to show issues before/during upgrades beyond alerts
• Do we need a UI for overriding backpressure blocking an upgrade?

Some of the answers will depend on what API will be available. Under the hood, the EUS upgrade will be a set of serial upgrades through each version.

Acceptance Criteria

• Reach agreement in coordination with other teams on what UI changes are needed to support EUS -> EUS upgrades
• Understand what APIs will be available and whether there are any gaps for the desired user experience. (Currently we only look at the ClusterVersion APIs.)
• Work with the UXD team to create designs for feedback
• Create stories for the actual implementation

cc rhn-support-sdodson pweil@redhat.com