CORS 2040: [gcp] Adding Public and Private Managed zones#6288
CORS 2040: [gcp] Adding Public and Private Managed zones#6288openshift-merge-robot merged 1 commit intoopenshift:masterfrom
Conversation
be08b33 to
7c4b87a
Compare
|
/assign |
jstuever
left a comment
There was a problem hiding this comment.
This is a great starting point. I think we should go ahead and pass the privateZone and publicZone string into the manifest "as is" while relying on the install-config for the validation. I'm also concerned about the Terraform records not knowing which project the managed_zone is in. And, I've recommended a slightly different parseZoneName() function. Other than that, some minor tweaks.
70afd37 to
4b75a6e
Compare
jstuever
left a comment
There was a problem hiding this comment.
Two minor tweaks.... 1) I think we need to be very prescribed with which projects the terraform dns records exist, and 2) I think we should be more prescribed with the parsing of the relative path managedZone names.
jstuever
left a comment
There was a problem hiding this comment.
There are some functional changes needed here.... and a couple of nit pick items.
jstuever
left a comment
There was a problem hiding this comment.
Looking great! Just a few more minor changes.
7857bb8 to
4c713b7
Compare
|
/cc @AnnaZivkovic |
|
/hold cancel |
jstuever
left a comment
There was a problem hiding this comment.
This appears to function as desired. I'll leave it to the rest of the team to review and approve.
**Install config added the public and private managed zones under platform/gcp **Install config validate the public and private managed zones (if provided) - when empty or "None" the validation does not occur. ** Added tests for install config ** config.Spec.PublicZone and config.Spec.PrivateZone in the cluster dns manifest are not set when "None", Default (empty) values for Public and Private managed zones will not change the current behavior (zones are created and managed in the ProjectID) ** Added the terraform values to skip the creation of public and private zones and their records according to the data provided in public/privateManagedZones: "" (default): normal behavior "None": skip private and public zone and record creation Data Provided: Skip zone creation but still create the records for the zone(s). ** Terraform will use the project or network project ID when creating zones and records.
|
@barbacbd: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: patrickdillon The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| description: ID Technology Preview. ID or name of the zone. | ||
| type: string | ||
| project: | ||
| description: ProjectID Technology Preview When the ProjectID |
There was a problem hiding this comment.
Nit. Missing a period here Preview "." When.
There was a problem hiding this comment.
well its tech preview does it matter = )
| description: ID Technology Preview. ID or name of the zone. | ||
| type: string | ||
| project: | ||
| description: ProjectID Technology Preview When the ProjectID |
There was a problem hiding this comment.
| privateZoneName := "" | ||
| privateZoneProject := "" | ||
| if installConfig.Config.GCP.PrivateDNSZone != nil && installConfig.Config.GCP.PrivateDNSZone.ID != "" { | ||
| createPrivateZone = false |
There was a problem hiding this comment.
This seems counter intuitive to me. When PrivateDNSZone != nil and the ID is provided, we don't create private zones?
There was a problem hiding this comment.
no that means that one exists already we DO NOT want to create one. We are assuming it is already created and provided by the user. This option of adding the privateDNSZone.ID is not to name a new private zone but to use an existing one.
There was a problem hiding this comment.
Ok. Got it. I think I was equating createPrivateZone with what createPrivateZoneRecords is doing.
|
/lgtm |
|
/skip |
|
/override ci/prow/e2e-azure-ovn |
|
@barbacbd: Overrode contexts on behalf of barbacbd: ci/prow/e2e-azure-ovn DetailsIn 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 kubernetes/test-infra repository. |
**Install config added the public and private managed zones under platform/gcp
**Install config validate the public and private managed zones (if provided) - when
empty or "None" the validation does not occur.
** Added tests for install config
https://issues.redhat.com/browse/CORS-2040