Epic Goal

• Enable external-dns-operator for aarch64

Why is this important?

• hypershift-cli uses external-dns-operator in their QE pipelines, we have added support for aarch64 in AWS for Hosted Control Planes and currently QE pipelines are blocked until this is enabled.
• ROSA HCP, self managed AWS, and Azure will need this as part of setting up externalDNS.

Scenarios

1. As a QE Engineer working on Hosted Control Planes, I want to successfully enable the full QE test suite for HCP (including using hypershift-cli) for aarch64.

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. Builds enablement
2. QE

Previous Work (Optional):

1. The ARM Enablement Team scoped this work out as having no outstanding dependencies & only minor build changes required:
   https://docs.google.com/presentation/d/1UyPiSkV1ufF-wIgMAyr3tgSNVT1Uw58yBly1opkKJZM/edit#slide=id.g115475fc5c2_0_0  

Open questions::

1. None

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>