DoD:

• For every alert from a given set, if it is in firing status, there is an element in “status.conditionalUpdateRisks”.
• An update is accepted if and only if all of its risks, including the ones converted from a firing alerts, are accepted, i.e., in clusterversion.spec.desiredUpdate.acceptRisks.

Implementation ideas:

• see how oc-cli retreives the firing alerts.
• if a firing alert, e.g., ClusterOperatorDown, is in the set, then status.conditionalUpdateRisks contains the following element:

name: ClusterOperatorDown # name of the alert    
message: alert.Annotations.Summary    
url: https://hostname/monitoring/alertrules/2881187465 # the link to the alert detail page    
matchingRules: # the expression of the alert rule    
conditions:    
- status: True      
  type: Apply      
  reason: Alert:firing      
  message: critical alert ClusterOperatorDown firing … # the details in oc-cli      
  lastTransitionTime: alert.ActiveAt 

If more than one firing alert matching the name, we aggregate their details into conditions[0].message and use the oldest ActiveAt as lastTransitionTime.