Value Statement

Allow flexibility for how users will access the API server of their OpenShift Virtualization HCP clusters.

Definition of Done for Engineering Story Owner (Checklist)

• When deploying a new cluster using OpenShift Virtualization, the user can choose LoadBalancer or NodePort for the API server publishing strategy

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.

Additional Information

AI HyperShift wizard can be used as guide for YAML template:
https://github.com/stolostron/console/blob/main/frontend/src/routes/Infrastructure/Clusters/ManagedClusters/CreateCluster/templates/assisted-installer/hypershift-template.hbs#L58-L71

AI implementation (for copy):
https://github.com/openshift-assisted/assisted-installer-ui/blob/master/libs/ui-lib/lib/cim/components/Hypershift/HostedClusterWizard/NetworkStep/NetworkForm.tsx#L29-L100