We must be able to test Hosted Control Planes for RHOSO in a representative environment. The target environment should be identical to an expected RHOSO deployment in all important ways.

It may be worth integrating with the RHOSO CI pipeline for this.

We decided to change the scope of this EPIC to not cover RHOSO.

• DP or TP

• (eduen) with all the uncertainty on use cases and lack of parity features, I believe we should Dev Preview it in 4.18, maybe TP in 4.19 and GA in 4.20

• CI - Epic to cover deployment of HCP, mgmt cluster will be on BM (targetting RHOSO), guest cluster will be deployed in OSP cloud deployed by RHOSO. Since Dev doesn’t have RHOSO running and QE does, that might be more suitable for QE
• Deploying HCP Operator on the same BM cluster for the RHOSO CP is not currently implemented
• How can we make the architecture work at scale
• How can we improve isolation
• Separate workloads on different workers
• Separate HCP CP (etcd) from RHOSO mgmt cluster and RHOSO operators

• We could use Director based OSP as the proving ground for future RHOSO use cases, AND Director OSP has more potential customers capable of testing HCP

• Current supported configurations for HCP is VERY basic
• Conclusion - update this Epic to be basic use cases on OSP 17.1
• Dev uses AWS Route 53 to record DNS record for Ingress. Updating record for ingress is currently a Day 2 operation but will be changed in the future. Once you deploy cluster you have to wait before you update the ingress IP record then you can run the conformance tests