Epic Goal

• While deploying OpenShift to a shared VPC (XPN) in GCP the user will be able to bring their own DNS zone where to create the required records for the API server and Ingress.

Why is this important?

• Missing this capability of providing an existing hosted zone while deploying OpenShift to a shared VPC in GCP will force customers to provision the required infrastructure to deploy OpenShift to a shared VPC instead of leveraging the Installer to automatically create all the required objects resulting in a poor UX

Scenarios

1. The user will be able to provide an existing DNS zone when deploying OpenShift to a shared VPC (XPN) in GCP that will be used to host the required DNS records for the API server and Ingress.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.

Previous Work (Optional):

1. OCPBU-10
2. CORS-2474

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>