Follow up on OTA-791 and OTA-924.

Phase 2: The conditional updates should work for hosted control planes in managed HyperShift.

Epic Goal*

The OTA team is going to manage versions for managed clusters as part of the OCPSTRAT-777 feature. The managed clusters, including managed HyperShift clusters, will consume update recommendations from the OpenShift Update Service (OSUS).

Today, the individual configuration of each managed cluster is not considered as a part of update recommendations.  The side effect is conditional risks cannot be applied correctly.

In the future, the hosted CVO in a managed HyperShift cluster will consume update recommendations directly from OSUS. This will enable it to properly apply conditional risks.

The goal of this Epic is to enable the hosted CVO in a managed HyperShift cluster to evaluate conditional risks by considering its hosted control plane configuration.

Why is this important? (mandatory)

This Epic will provide a positive user experience by evaluating conditional risks correctly per individual cluster’s configuration.

Scenarios (mandatory)

1. As a managed HyperShift customer, I am able to update my hosted cluster appropriately to a release containing conditional risks because the risks were correctly evaluated by considering my cluster’s configuration, and the risks do not affect my hosted cluster.

Dependencies (internal and external) (mandatory)

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

This may be affected by a design document that will be created and reviewed.

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 - 
• Documentation -
• QE - 
• PX - 
• Others -

This may be affected by a design document that will be created and reviewed.

Acceptance Criteria (optional)

The hosted CVO in a managed HyperShift environment is capable of consuming update recommendations from OSUS and can evaluate conditional risks correctly.

Drawbacks or Risk (optional)

N/A

Done - Checklist (mandatory)

• CI Testing - Tests are merged and completing successfully
• QE - Test scenarios are written and executed successfully.