Epic Goal

Make sure the oc adm upgrade status CLI client-side prototype implementation, as delivered in Tech Preview in 4.16 and extended in 4.17, is promoted to GA.

Why is this important? (mandatory)

OTA-1260 effort failed, leading to an absence of a meaningful near-term cluster-side deliveries to improve the OCP update experience for our customers. In that absence, it was decided that promoting the existing client-side implementation may allow us to deliver at least some value near-term, while we continue searching for other medium-term solutions.

Scenarios (mandatory) 

• Cluster administrator wants a tool they can use to monitor a cluster update progress
• Cluster administrator wants a tool they can use to monitor a cluster update health
• Cluster administrator wants a tool they can use to troubleshoot a cluster update problem

Dependencies (internal and external) (mandatory)

No dependencies on other team except maybe help by Workloads and TRT team on how to implement CLI tests to be run during an update

Contributing Teams(and contacts) (mandatory) 

Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

• Development - OTA
• Documentation - OTA
• QE - OTA
• PX - 
• Others -

Acceptance Criteria (optional)

• oc adm upgrade status is promoted to GA

Drawbacks or Risk (optional)

• The oc adm upgrade status client-side prototype was built with an intent that it would never be shipped beyond TP (the client-side logic was supposed to get replaced by server-side API delivered in OTA-1260) and there are known implementation, form factor, extensibility and maintenance tradeoffs and constraints. The decision to still pursue GA was made with this knowledge.

Done - Checklist (mandatory)

The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

• CI Testing - Tests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Other