(description in progress)

{}USER STORY:{}

As a Developer, I want to increase the coverage of the Local Zones location on CI, so I can make sure we are testing a different location every time the CI is running.

{}DESCRIPTION:{}

Currently the e2e is provisioning the cluster, adding the Local Zone location based on the subnet's zone (parent zone), fixed value.[1]

We could increase the coverage by getting ramdomly the zoneName when listing the zones, something like

$ aws --region us-east-1 ec2 describe-availability-zones --filters Name=opt-in-status,Values=opted-in Name=zone-type,Values=local-zone |jq -r .AvailabilityZones[].ZoneName | shuf |head -n1
us-east-1-scl-1a

$ aws --region us-east-1 ec2 describe-availability-zones --filters Name=opt-in-status,Values=opted-in Name=zone-type,Values=local-zone |jq -r .AvailabilityZones[].ZoneName | shuf |head -n1
us-east-1-bos-1a

(...) 

So for each execution we could get a different zone to provision the cluster, running e2e on that zone.

Over the time we may have a good coverage on the given region.

{}Required:{}

...

{}Nice to have:{}

...

{}ACCEPTANCE CRITERIA:{}

TBD

{}ENGINEERING DETAILS:{}

[1] https://github.com/openshift/release/blob/master/ci-operator/step-registry/aws/provision/localzone-subnet/aws-provision-localzone-subnet-commands.sh#L116-L125