<--- Placeholder, this Epic requires refinement --->

Epic Goal

• Create e2e tests on CAPA project to cover AWS Local Zones[1] and AWS Wavelength Zones[2] delivered on 4.16
  • [1] https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/4882 
  • [2] https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/4901 
• When the e2e is delivered, we can get completeness of issue: https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/4874 

Why is this important?

• As part of Red Hat commitment of upstream contribution, we agree to write e2e test on CAPA project when we delivered the support of edge zones (Local Zones and Wavelength Zones) to 4.16, included in CAPA v1.25

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

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 - Downstream documentation merged: <link to meaningful PR>