User story:

Because VPNs are required for hosted (hypershift) control plane clusters, as a user, I don't want to see the option to select/deselect a VPN

Acceptance criteria:

• If it is a hosted (hypershift) control plane, the user will not be given the option to select a VPC. The VPC step in the wizard shall not be shown.
• If it is a hosted (hypershift) control plane, the user will not be given the option to use "private links"
• For hosted (hypershift) clusters, there shall be an alert notifying users that private links will be used
•  The “next” button will not go to the next action unless all required fields pass validation
• The Network/VPC step will not be shown for hosted (hypershift) clusters
• Data entered will be shown on the review page (both standalone and hosted ROSA wizards)
• [technical] Data is prepared to be sent to the api

Mockups:

Mockups | PD 1434

NOTE The Install into a Virtual Private Cloud (VPC) will look/behave the same regardless if “public” or “private” is selected for hosted (hypershift) control planes.

------------------------------------------------------------------------------------

Implementation details:

Summary:

For the most part, certain options will be removed if the control plane is hosted (hypershift).  There will be some text specific to a hosted control plane

Major tasks:

• Add text and an information alert for hosted (hypershift) control planes.
• Hide the option for VPN
• Add ability to add public subnet(s) if the a public cluster privacy
• Hide the option for the private link - private links are always used for hosted (hypershift) clusters.

Notes:

• The mock-ups show it, but there isn't a “VPC” settings wizard step for hypershift (hosted) clusters. In addition, they are missing a control plane step (step 2)

More research needed:

• What additional tacking (if any) is needed for hosted (hypershift) control planes?