-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18.0
-
None
-
Installer, OpenShift API and Ingress Operator changes for AWS LB IPs
-
BU Product Work
-
False
-
None
-
False
-
Green
-
In Progress
-
OCPSTRAT-992 - [Tech Preview]: Allow customer managed DNS solutions for AWS: Implementation
-
OCPSTRAT-992[Tech Preview]: Allow customer managed DNS solutions for AWS: Implementation
-
25% To Do, 8% In Progress, 67% 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
- For a customer provided DNS to be utilized with AWS platforms, the Installer should be updated not configure the default cloud provided DNS (Route 53). Installer is also responsible for updating the Infrastructure config resource and bootstrap ignition with the LB IPs for API and API-Int. These would be used to stand-up in-cluster CoreDNS pods on the 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>