OCP/Telco Definition of Done
Epic Template descriptions and documentation.

<--- Cut-n-Paste the entire contents of this description into your new Epic --->

Epic Goal

• Allow the custom DNS feature to be enabled on day 2 by modifying the Infrastructure CR.

Why is this important?

ARO already has its own mechanism for implementing custom DNS. Enabling the in-cluster DNS for new installs will only partially enable this mechanism to be turned off. To get rid of it entirely, existing clusters must be switched over to use the new custom DNS functionality for core OCP.

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. Some of the design details are being worked on in ARO: CoreDNS Plugins in HCM WD

Previous Work (Optional):

1. …

Open questions::

1. How do we update the pointer ignition to reference the IP address of the internal load balancer instead of api-int for fetching the ignition?

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>