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

• This is related to https://issues.redhat.com/browse/RFE-2085 . The request is for a feature to change what IP address our internal DNS records like api-int point at.

Why is this important?

• This would allow customers to send internal cluster traffic to their preferred external loadbalancer.

Scenarios

1. As a cluster admin, I want to send all cluster traffic through my shiny external loadbalancer, including internal cluster traffic.

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. ...

Previous Work (Optional):

1. We looked into this as part of the external loadbalancer work, but at the time decided not to pursue it because the api-int record is critical to new nodes joining the cluster. However, at that time the intention was that we would remove the internal loadbalancer completely, in which case the default api-int target would stop working. If we left the internal loadbalancer available for bootstrapping nodes but allowed a later override of the records once the node has come up that may be more feasible.

Open questions::

1. …

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>