XML

Word

Printable

Type: Epic
Resolution: Done
Priority: Undefined
Fix Version/s: openshift-4.20
Affects Version/s: None
Component/s: None
Labels:
- CORS:Green
- hygieneaug28

Epic Name:
GCP DNS Separate Project
Activity Type:
Product / Portfolio Work
Parent Link:
OCPSTRAT-1182Enable OCP on GCP XPN deployments to support DNS Zones in a third separated project
Hierarchy Progress Bar:

0% To Do, 6% In Progress, 94% Done
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Color Status:
Not Selected
Status Summary:

Hide

7/8/2025 -

Status: Green

Currently held up trying to get the installation to work. The problem appears to be the missing *.apps DNS record creation. I don't see this in either the private or public zones. This is the case for basic installs too as I changed the format for the dns zone name. The ingress operator should be able to handle it but it doesn't appear to be the case currently.

6/18/2025 -

Status: Green

The enhancement has been made. The start to the install config and validation work has been opened in a PR as a Proof of Concept. The original work was completed as part of the shared vpc work. Some of this work is being taken and reworked.

Show
7/8/2025 - Status: Green Currently held up trying to get the installation to work. The problem appears to be the missing *.apps DNS record creation. I don't see this in either the private or public zones. This is the case for basic installs too as I changed the format for the dns zone name. The ingress operator should be able to handle it but it doesn't appear to be the case currently. 6/18/2025 - Status: Green The enhancement has been made. The start to the install config and validation work has been opened in a PR as a Proof of Concept. The original work was completed as part of the shared vpc work. Some of this work is being taken and reworked.
Size:
None

Target Version:

openshift-4.20
Release Blocker:
None

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

Allow users to specify a separate project for DNS creation

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

Does this apply to private DNS?

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>