-
Notifications
You must be signed in to change notification settings - Fork 508
CORS-4102: enhancement for GCP DNS Management in another project #1810
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
@barbacbd: This pull request references CORS-4102 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
20951d7
to
8973925
Compare
/cc @JoelSpeed |
/test markdownlint |
2 similar comments
/test markdownlint |
/test markdownlint |
** this change is an enhancement doc for OCPSTRAT-1182. The DNS management for GCP XPN (Shared VPC) installs should be able to live in a third project. This third project is considered a second service project.
@barbacbd: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
** this change is an enhancement doc for OCPSTRAT-1182. The DNS management for GCP XPN (Shared VPC) installs should be able to live in a third project. This third project is considered a second service project.