User story:

So that I can set up my hosted ROSA (hypershift) cluster correctly, as a user I want etcd encryption not to be available in because etcd isn't yet supported.

Acceptance criteria:

• The details section will be placed as the first sub-option of the third option (Cluster details) if the user has access to the feature gate (HAC 2415)
• The following parts of the details section will behave like the ROSA stand-alone wizard:
  • Cluster name
  • Version
  • Region
  • Availability (single vs multi-zone)
  • Monitoring
• If the user selects “uses custom KMS keys”, the user will be required to enter a properly formatted key ARN (current functionality)
• The “next” button will not go to the next action unless all required fields pass validation (current functionality)
• For a hosted control plane (aka hypershift), the option to add etcd encryption shall not be available.
• Data entered will be shown on the review page (current functionality)
• [technical] Data is prepared to be sent to the api on cluster creation (current functionality)

Mockups:

Mockups:https://docs.google.com/document/d/12PYQiNf0YP8LEkczMHEeyx91AXFbKGa-hD1Fh4gSKWQ/edit#heading=h.ulp2uf90mwj

NOTE: 
All layout changes are not part of this story - they are covered in HAC 2520

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

Implementation details

Summary:

Hide the etcd encryption option if the control plane is hypershift.  Assume it is not checked when sending data to form submission.

Major tasks:

• Hide the “Enable addition etcd encryption” for hosted (hypershift) control plane clusters

Notes:

• Design and microcopy have not been finalized

More research needed:

• What data for etcd is sent (if anything) to the back-end for hosted (hypershift) control plane