Epic Goal

• Admins can create compute pool named `edge` on the AWS platform to setting up Local Zone MachineSets.
• Admins can select and configure subnets on Local Zones before cluster creation.
• Ensure the installer allows creating a new machine pool for `edge` workloads
• Ensure the installer can create the MachineSet with `NoSchedule` taints on edge machine pools.
• Ensure Local Zone subnets will not be used on `worker` compute pools or control planes.
• Ensure the Wavelength zone will not be used in any compute pool
• Ensure the Cluster Network MTU manifest is created when Local Zone subnets are added when installing a cluster in existing VPC

Why is this important?

• …

Scenarios

User Stories

• As a cluster admin, I want the ability to specify a set of subnets on the AWS
  Local Zone locations to deploy worker nodes, so I can further create custom
  applications to deliver low latency to my end users.

• As a cluster admin, I would like to create a cluster extending worker nodes to
  the edge of the AWS cloud provider with Local Zones, so I can further create
  custom applications to deliver low latency to my end users.

• As a cluster admin, I would like to select existing subnets from the local and
  the parent region zones, to install a cluster, so I can manage networks with
  my automation.

• As a cluster admin, I would like to install OpenShift clusters, extending the
  compute nodes to the Local Zones in my day zero operations without needing to
  set up the network and compute dependencies, so I can speed up the edge adoption
  in my organization using OKD/OCP.

Acceptance Criteria

• The enhancement must be accepted and merged
• Release Technical Enablement - Provide necessary release enablement details and documents.
• The installer implementation must be merged

Dependencies (internal and external)

Previous Work (Optional):

1. https://issues.redhat.com/browse/SPLAT-635 

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>