OCP/Telco Definition of Done
https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
Epic Template descriptions and documentation.
https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
ACM-wide Product Requirements (Top-level Epics)
https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit

*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*

Epic Goal

Support more configuration options for deployment of hosted control plane clusters on OpenShift Virtualization

Why is this important?

The UI needs to maintain feature parity with what can be accomplished using the HCP cli. These advanced fields let people configure HCP OpenShift Virtualization from within the web console without needing to lean on the cli.

Scenarios

1. Networking - select API server publishing strategy (NodePort or LoadBalancer service type) (Not yet supported)
2. Node pools - select Infrastructure availability policy (choice of Highly available or Single replica)
3. OpenShift Virtualization - allow user to use an external infra cluster (KubeVirt VMs are hosted on a cluster different from the one hosting Hosted Control Plane components) by providing a kubeconfig and namespace.
4. KubeVirt CSI Storage Class Mapping
5. Network Options (Per NodePool)

See details in ACM 2.12 To Do - UI HCP KubeVirt Notes

For API specs, use:
HostedCluster
NodePool
Can paste these into https://editor.swagger.io/ to read specs.

More up-to-date API docs.

Acceptance Criteria

User can request deployment of an HCP cluster on OpenShift Virtualization with the options listed above. This may be achieved by adding these options in the cluster creation wizard and/or credentials wizard (for external infrastructure option).

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.