Epic Goal*

What is our purpose in implementing this?  What new capability will be available to customers?

When cluster admins inspect the available updates, they can see the firing alerts as risks that might impact the update.

Why is this important? (mandatory)

What are the benefits to the customer or Red Hat?   Does it improve security, performance, supportability, etc?  Why is work a priority?

Scenarios (mandatory) 

Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

What a cluster admin usually does before a cluster update includes

• Check the available updates to the cluster via the status of the "clusterversion/verson" manifest, or `oc adm upgrade recommend`, and evaluate their risks and then decide if the cluster is upgraded to that update.
• Check the critical alerts firing on the cluster and estimate their impact and resolve them if needed.

This epic includes those alerts as risks exposed to updates to reduce the number of places that a cluster admin has to check.

Dependencies (internal and external) (mandatory)

What items must be delivered by other teams/groups to enable delivery of this epic.

The implementation does not need any extensions of openshift/api.  The code changes are going to be in the CVO repo which the OTA team owns and in the openshift/oc repo which is not owned by the OTA team.

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 - the OTA doc team
• QE - OTA
• PX - 
• Others -

Acceptance Criteria (optional)

• A given set of alerts (starting from the ones that oc handles and could grow on demand) are populated in "clusterversion.status.conditionalUpdateRisks" if any alert is in firing state.
• An update is accepted if and only if all of its risks, including the ones converted from a firing alerts, are accepted. 

Drawbacks or Risk (optional)

Reasons we should consider NOT doing this such as: limited audience for the feature, feature will be superseded by other work that is planned, resulting feature will introduce substantial administrative complexity or user confusion, etc.

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