-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18.0
-
None
-
None
-
Provide in-cluster DNS resolution for *.apps
-
BU Product Work
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-992 - [Tech Preview]: Allow customer managed DNS solutions for AWS: Implementation
-
-
100% To Do, 0% In Progress, 0% Done
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
- cluster-ingress-operator should not configure the cloud default DNS for *.apps DNS resolution. Instead, the Ingress LB IPs should be added to the Infra CR. MCO uses this LB information to render the Corefile and CoreDNS pod on bootstrap and control plane nodes.
Why is this important?
- …
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
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>