CVO to drive the hypershift hosted control plane

Epic Goal*

The intent is to remove some of the work HSO currently doing to start a HCP (hosted control plane), so HSO will start the CVO for a HCP and let CVO drive it. The benefit of this would be that we have to maintain a single CVO  code base which will be running both in HCP environments and in standalone OCP instances.

As discussed in the OTA f2f https://drive.google.com/file/d/1ED7DwJoUi8VVVn4F9b2yS5swiDAiUGul/view (this is specially discussed after 35:00)

Once CVO drive the hosted control plane the following things will be handled by CVO as it currently done for standalone OCP clusters.

• Validating a signature for the target release image.
• Verifying Upgradeable and other preconditions to see if the update seems safe.
• Checking to see if any ClusterVersion capabilities should be implicitly enabled, by comparing the outgoing and incoming manifest sets.
• Storing any concerns (e.g. matching update risks) in acceptedRisks.

This epic has been created as a result of the spike OTA-823.

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.  

Dependencies (internal and external) (mandatory)

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

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 -

Acceptance Criteria (optional)

Provide some (testable) examples of how we will know if we have achieved the epic goal.  

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