Epic Goal

• Enable users to specify a pre-existing DNS zone from any project for managing internal DNS.
• Enable users to specify a pre-existing DNS zone from any project for managing external DNS.
• Rescoping this epic to be only for bringing existing DNS zones within the same project. Cross-project zones has been moved to 4.13.

Why is this important?

• To enable greater flexibility for where the DNS zones live
• To enable future to enable Shared VPC clusters to be provisioned using the IPI workflow.

Scenarios

1. The DNS zone for the internal DNS records can be specified in the install config and the cluster will be configured to use it.
2. The DNS zone for the external DNS records can be specified in the install config and the cluster will be configured to use it.

Acceptance Criteria

• Release Technical Enablement - Provide necessary release enablement details and documents.

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>