Epic Goal

The External DNS Operator deploys and manages ExternalDNS to provide name resolution for services and routes from the external DNS provider to OpenShift Container Platform.

This epic turns on the flag and adds testing on the Power environment.

Why is this important?
Customers with existing DNS Services can use them in a Power OpenShift to integrate with routes.

Scenarios
As a cluster-admin, I install the External DNS operator.
As a cluster-admin, I uninstall the External DNS operator.
As a developer, I add a route and I can craft an ExternalDNS entry automatically.
As a developer, I add a service and I can craft an ExternalDNS entry automatically.

Acceptance Criteria
The scenarios are passed.
The operator hub is updated.
The docs are updated.

Dependencies (internal and external)
The ExternalDNS Operator team must buy in. It should be only done downstream in OpenShift changing the CSV supported arch.

1. From a technical or non-technical perspective, what is required from/of the team ? Review a PR to update the bundle.
2. Have they formally aligned to the plan/requirement for MultiArch to complete this ticket in 4.22 ? I've asked.
3. What's the associated Dependency date(s) ? Not sure what this question is asking
4. Can their related Jira ticket(s) be linked from this epic for transparency ? No related JIRA.

Previous Work (Optional)
Power Team tested with the existing images in catalog.redhat.com.

Open questions
n/a

Done Checklist

• CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
• 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 - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
• QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
• QE - Automated tests merged: <link or reference to automated tests>
• QE - QE to verify documentation when testing
• DOC - Downstream documentation merged: <link to meaningful PR>
• All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.