This EPIC regroups the tasks that need to be finished so we can deliver Hosted Control Plane on OpenStack as TechPreview.

Some tasks were initially in this EPIC and were de-prioritized to be done later once we have customer feedback. What remain in the current list are things we think can be achieved within the 4.19 cycle.

This EPIC will be used by QE to test the quality of the product and the outcome will have a direct impact on whether this can be TechPreview or now. The HCP team will only accept it as TechPreview if we have QE coverage.

The initial scenario that QE agreed to start with is the following:

• OpenStack management cluster deployed via a ShiftOnStack cluster (a regular cluster), on any supported version of OSP (17.1 or 18.0 at this point). The cluster is using a dedicated OpenStack project (e.g. hcp-hub).
• One or multiple HostedClusters deployed on one or multiple namespaces using different projects for the Nodepools and the OpenStack resources associated with the Hosted Clusters (e.g. hcp-spoke1, hcp-spoke-2, etc).
• The use case is described and drawn here: https://docs.google.com/document/d/178_FTiLCnMBfAdDoaqm15YCuBkNof7SGZueBZOx1cTE/edit?tab=t.0
• Against that HostedCluster, the regular OpenShift conformance suite can be executed (including CSI cinder and CSI manila). The OpenStack e2e tests can also be executed.
• Note: to execute the Hypershift e2e tests, an AWS account is required for dynamic DNS provisioning (route53).