Goal:

• Create CI step, and presubmit job running on installer PRs for AWS, to validate manifests created by installer for edge zones (Local and Wavelength Zones).

Test requirement:

• The test must run across all regions which support Local or Wavelength zones
• The test must create manifest (openshift-install create manifests) for each region with support of edge zones, and not limited by US ones (CI runs only in use1, and usw2).
• The test don't need to create a cluster, for that reason it can pin the LEASE_POOL (Region), or just ignore it and: discover, and iterate across regions.
• The test must increase the coverage of supported configuration: single zone type, mixed zone, full zones
• Validate if the machineset manifests for edge zones have been filled the instance type, edge zone labels, and taints
• The job must run 4.15+ for Wavelength and Local Zones. Nice to have 4.14 for Local Zones only

Motivation:

AWS is quickly expanding and changing edge zones (Local and Wavelength Zones). Overall the edge-zones implementation is splitted in:

• Create infra resources to extend the machines to edge zones (executed by installer)
• Create the machines from manifest created by installer (executed by MAPI)

Considering we are supporting edge zones across all AWS regions which supports it, and not limited to US, and we are testing only in US zones, we need to find the way to mitigate the failures in non-US zones, without increasing CI costs.

Bugs opened on installer that could be prevented by that proposal:

• OCPBUGS-27737
• OCPBUGS-23039

Open Questions:

• [1] Which CI profile we'll be able to run?
  • The job will not create infrastructure, but the validation and manifest generation process requires access to AWS API. Currently the default profile (aws) does not have all regions enabled (opted-in), impacting in the goal of this job as the EC2 Instances Offerings API does not return data when the zone is not enabled in the region.
  • Example of listing regions for default CI profile - field status with value "not-opted-in" points to disabled regions:

INFO[2024-02-10T01:34:01Z] 2024-02-10 01:33:51+00:00 - Discovering regions
REGION        STATUS
ap-south-2    not-opted-in
ap-south-1    opt-in-not-required
eu-south-1    not-opted-in
eu-south-2    not-opted-in
me-central-1    not-opted-in
il-central-1    not-opted-in
ca-central-1    opt-in-not-required
eu-central-1    opt-in-not-required
eu-central-2    not-opted-in
us-west-1    opt-in-not-required
us-west-2    opt-in-not-required
af-south-1    not-opted-in
eu-north-1    opt-in-not-required
eu-west-3    opt-in-not-required
eu-west-2    opt-in-not-required
eu-west-1    opt-in-not-required
ap-northeast-3    opt-in-not-required
ap-northeast-2    opt-in-not-required
me-south-1    not-opted-in
ap-northeast-1    opt-in-not-required
sa-east-1    opt-in-not-required
ap-east-1    not-opted-in
ca-west-1    not-opted-in
ap-southeast-1    opt-in-not-required
ap-southeast-2    opt-in-not-required
ap-southeast-3    not-opted-in
ap-southeast-4    not-opted-in
us-east-1    opt-in-not-required
us-east-2    opt-in-not-required