User Story:

As a user, I want to be able to:

• Use pre-existing public and/or private DNS zones
• or default to creating these zones in the service project (projectID) when not specified (ie. "")

so that I can achieve

• Creating an IPI cluster using Shared VPC where the DNS zones live in the Host Project,
• or creating an IPI cluster using a Shared VPC with insufficient permissions to create DNS resources in the Host Project,
• or creating an IPI cluster using a Shared VPC where the zones are fully managed in the service project.

Acceptance Criteria:

Description of criteria:

• Install config parameters exists and are validated
  • platform.gcp.privateManagedZone
  • platform.gcp.publicManagedZone
• When empty (default), the DNS zones will be created and managed in the Service Project (projectID).
• When zone(s) are specified, the DNS records will be created and managed using the specified zones.
  • The Terraform DNS zones will not be created
  • The Terraform DNS records will be created in the specified zone(s)

(optional) Out of Scope:

Creating the networkProjectID install config parameter belongs to another story, intended to be consumed by this one.

Updating the in-cluster DNS mechanics to be able to use the host project belongs in another story.

Updating the cluster dns manifest to specify the config.Spec.PublicZone and config.Spec.PrivateZone will be done in an different story.

Engineering Details:

• https://github.com/openshift/installer/blob/master/data/data/gcp/cluster/dns/base.tf
• https://github.com/openshift/installer/blob/72b7bb82de6986643d8bf5b9ed67ccf954aaadb2/pkg/asset/manifests/dns.go#L136-L144
• https://github.com/openshift/api/blob/master/config/v1/types_dns.go#L68