In the Discovery Options section of the Google Cloud Platform (GCP) Setup page, you configure the information that you want to import from the GCP infrastructure and how you want to import it.
Discover GCP Resources options
| Field/Option | Description |
|---|---|
| GCP VPC/Subnets | Select this option to import all GCP private VPC and subnet
address space information. The private VPCs and subnets are
converted into IPv4 blocks and networks on Address Manager. Note:
|
| GCP Public IP Ranges | Select this checkbox to import all GCP public address space information. The public IP ranges are converted into IPv4 and IPv6 blocks and networks on Address Manager. |
| GCP VM Instances | Select this checkbox to import all VM instance information. The VM instances are converted into devices on Address Manager. |
| GCP Load Balancers | Select this checkbox to import all load balancer
instance information. The load balancer instances are converted into
devices on Address Manager. Note: This option
supports only importing of VM Instances and VM Instance
Groups.
|
| GCP Cloud DNS (Private Zones) | Select this checkbox to import all private DNS zone record information. The DNS zone records are converted to private DNS records on Address Manager. |
| GCP Cloud DNS (Public Zones) | Select this checkbox to import all public DNS zone record information. The DNS zone records are converted to public DNS records on Address Manager. |
| GCP Kubernetes Engine | Select this checkbox to import all GCP Kubernetes Engine (GKE) resources, including Clusters and Node pools. The GCP Kubernetes Clusters are converted into device types on Address Manager and Nodegroups are converted into tags. |
| GCP Private
Endpoints Endpoint View |
Select this checkbox to import private endpoint DNS
record information. The private endpoints are converted into private
endpoint DNS records on Address Manager with the prefix defined in
the BlueCat Target Zone field. Also, in Endpoint View, enter the name of the view that will be created in Address Manager; or select an existing view in Address Manager that will contain the GCP private endpoint information. Note: If you select a configuration that already exists in
Address Manager, all views within that configuration are
populated in this field.
|
| GCP DNS Hostnames -
Internal DNS Hostname Internal View |
Select this checkbox to import internal DNS record
information. The internal DNS records are converted into internal
DNS records on Address Manager with the prefix defined in the
BlueCat Target Zone field. Also, in
DNS Hostname Internal View, enter the
name of the view that will be created in Address Manager or
select an existing view in Address Manager that will contain the
internal GCP-provided name resolution information.
Note: If you
select a configuration that already exists in Address
Manager, all views within that configuration are populated
in this field.
|
| GCP DNS Hostnames -
External DNS Hostname External View |
Select this checkbox to import external DNS record information.
The external DNS records are converted into external DNS records on
Address Manager with the prefix defined in the BlueCat
Target Zone field. In DNS Hostname
External View, enter the name of the view that
will be created in Address Manager or select an existing view in
Address Manager that will contain the external GCP provided name
resolution information.
Note: If you select a configuration that
already exists in Address Manager, all views within that
configuration are populated in this
field.
|
| Dynamic Update of DNS Resource Records | This option is available only when connecting to Address Manager v9.4.0 or later. Select this checkbox to update the DNS records in Address Manager and automatically deploy the changes to the primary BDDS of that zone using selective deployment. This checkbox is disabled by default and available only if you select the Enable Visibility after Discovery checkbox. Attention: You must perform a full DNS deployment to the managed BDDS
before any subsequent selective deployments can be performed.
If you configure the managed BDDS to manage the cloud infrastructure exclusively, you can perform a discovery job to import the cloud infrastructure into your Address Manager. After view and zone information are successfully imported into Address Manager, you can configure primary and secondary DNS roles for the selected managed BDDS and perform a full DNS deployment. Once the DNS data is deployed to the managed BDDS, you can enable the visibility job to continuously monitor changes to your cloud DNS infrastructure and selectively deploy those changes to the managed BDDS. |
BlueCat Target Zone options
| Field/Option | Description |
|---|---|
| BlueCat Target Zone | Enter the name of the DNS zone on Address Manager that will contain the VM instance of DNS records. |
| Auto Create Zones | Select this checkbox to embed GCP projects for VM Instances and GCP project names for Load Balancers into the Provided Name Resolution. |
Other options
| Field/Option | Description |
|---|---|
| Remove Deleted Resources (Tag Deleted Views/Zones during Rediscovery) |
Select this checkbox to automatically delete resources (except for DNS Views and Zones) that currently exist in Address Manager, but were not found upon rediscovery. Missing View and Zone resources will be tagged for manual inspection and removal. For more details on viewing and manually deleting these tagged resources, see Deleting resources flagged as missing during rediscovery. |
| Dynamic Update of DNS Resource Records |
This option is available only when connecting to Address Manager v9.4.0 or later. Select this checkbox to update the DNS records in Address Manager and automatically deploy the changes to the primary BDDS of that zone using selective deployment. This checkbox is disabled by default and available only if you select the Enable Visibility after Discovery checkbox. Attention: You must perform a full DNS deployment to the
managed BDDS before any subsequent selective deployments can be
performed.
If you configure the managed BDDS to manage the cloud infrastructure exclusively, you can perform a discovery job to import the cloud infrastructure into your Address Manager. After view and zone information are successfully imported into Address Manager, you can configure primary and secondary DNS roles for the selected managed BDDS and perform a full DNS deployment. Once the DNS data is deployed to the managed BDDS, you can enable the visibility job to continuously monitor changes to your cloud DNS infrastructure and selectively deploy those changes to the managed BDDS. |