zecfoundation
/
cloud-foundation-fabric
mirror of https://github.com/ZcashFoundation/cloud-foundation-fabric.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
cloud-foundation-fabric/fast/stages/02-networking-nva/README.md

41 KiB
Raw Blame History

Networking with Network Virtual Appliance

This stage sets up the shared network infrastructure for the whole organization.

It is designed for those who would like to leverage Network Virtual Appliances (NVAs) between trusted and untrusted areas of the network, for example for Intrusion Prevention System (IPS) purposes.

It adopts the common “hub and spoke” reference design, which is well suited for multiple scenarios, and it offers several advantages versus other designs:

  • the "trusted hub" VPC centralizes the external connectivity towards trusted network resources (e.g. on-prem, other cloud environments and the spokes), and it is ready to host cross-environment services like CI/CD, code repositories, and monitoring probes
  • the "spoke" VPCs allow partitioning workloads (e.g. by environment like in this setup), while still retaining controlled access to central connectivity and services
  • Shared VPCs -both in hub and spokes- split the management of the network resources into specific (host) projects, while still allowing them to be consumed from the workload (service) projects
  • the design facilitates DNS centralization

Connectivity between the hub and the spokes is established via VPC network peerings, which offer uncapped bandwidth, lower latencies, at no additional costs and with a very low management overhead. Different ways of implementing connectivity, and related some pros and cons, are discussed below.

The diagram shows the high-level design and it should be used as a reference throughout the following sections.

The final number of subnets, and their IP addressing will depend on the user-specific requirements. It can be easily changed via variables or external data files, without any need to edit the code.

Networking diagram

Design overview and choices

Multi-regional deployment

The stage deploys the the infrastructure in two regions. By default, europe-west1 and europe-west4. Regional resources include NVAs (templates, MIGs, ILBs) and test VMs. This provides enough redundancy to be resilient to regional failures.

VPC design

The "landing zone" is divided into two VPC networks:

  • the trusted VPC: the connectivity hub towards other trusted networks
  • the untrusted VPC: the connectivity hub towards any other untrusted network

The VPCs are connected with two sets of sample NVA machines, grouped in regional (multi-zone) Managed Instance Groups (MIGs). The appliances are plain Linux machines, performing simple routing/natting, leveraging some standard Linux features, such as ip route or iptables. The appliances are suited for demo purposes only and they should be replaced with enterprise-grade solutions before moving to production. The traffic destined to the VMs in each MIG is mediated through regional internal load balancers, both in the trusted and in the untrusted networks.

By default, the design assumes the following:

  • on-premise networks (and related resources) are considered trusted. As such, the VPNs connecting with on-premises are terminated in GCP, in the trusted VPC
  • the public Internet is considered untrusted. As such Cloud NAT has been deployed in the untrusted landing VPC only
  • cross-environment traffic and traffic from any untrusted network to any trusted network (and vice versa) pass through the NVAs. For demo purposes, the current NVA performs simple routing/natting only
  • any traffic from a trusted network to an untrusted network (e.g. Internet) is natted by the NVAs. Users can configure further exclusions

The trusted landing VPC acts as a hub: it bridges internal resources with the outside world and it hosts the shared services consumed by the spoke VPCs, connected to the hub thorugh VPC network peerings. Spokes are used to partition the environments. By default:

  • one spoke VPC hosts the development environment resources
  • one spoke VPC hosts the production environment resources

Each virtual network is a shared VPC: shared VPCs are managed in dedicated host projects and shared with other service projects that consume the network resources. Shared VPC lets organization administrators delegate administrative responsibilities, such as creating and managing instances, to Service Project Admins while maintaining centralized control over network resources like subnets, routes, and firewalls.

Users can easily extend the design to host additional environments, or adopt different logical mappings for the spokes (for example, in order to create a new spoke for each company entity). Adding spokes is trivial and it does not increase the design complexity. The steps to add more spokes are provided in the following sections.

In multi-organization scenarios, where production and non-production resources use different Cloud Identity and GCP organizations, the hub/landing VPC is usually part of the production organization. It establishes connections with the production spokes within the same organization, and with non-production spokes in a different organization.

External connectivity

External connectivity to on-prem is implemented leveraging Cloud HA VPN (two tunnels per region). This is what users normally deploy as a final solution, or to validate routing and to transfer data, while waiting for interconnects to be provisioned.

Connectivity to additional on-prem sites or to other cloud providers should be implemented in a similar fashion, via VPN tunnels or interconnects, in the landing VPC (either trusted or untrusted, depending by the nature of the peers), sharing the same regional routers.

Internal connectivity

Internal connectivity (e.g. between the trusted landing VPC and the spokes) is realized with VPC network peerings. As mentioned, there are other ways to implement connectivity. These can be easily retrofitted with minimal code changes, although they introduce additional considerations on service interoperability, quotas and management.

This is an options summary:

  • VPC Peering (used here to connect the trusted landing VPC with the spokes, also used by 02-networking-vpn)
    • Pros: no additional costs, full bandwidth with no configurations, no extra latency
    • Cons: no transitivity (e.g. to GKE masters, Cloud SQL, etc.), no selective exchange of routes, several quotas and limits shared between VPCs in a peering group
  • Multi-NIC appliances (used here to connect the trusted landing and untrusted VPCs)
    • Pros: provides additional security features (e.g. IPS), potentially better integration with on-prem systems by using the same vendor
    • Cons: complex HA/failover setup, limited by VM bandwidth and scale, additional costs for VMs and licenses, out of band management of a critical cloud component
  • HA VPN
    • Pros: simple compatibility with GCP services that leverage peering internally, better control on routes, avoids peering groups shared quotas and limits
    • Cons: additional costs, marginal increase in latency, requires multiple tunnels for full bandwidth

IP ranges, subnetting, routing

Minimizing the number of routes (and subnets) in the cloud environment is important, as it simplifies management and it avoids hitting Cloud Router and VPC quotas and limits. For this reason, we recommend to carefully plan the IP space used in your cloud environment. This allows the use of larger IP CIDR blocks in routes, whenever possible.

This stage uses a dedicated /16 block (10.128.0.0/16), which should be sized to the own needs. The subnets created in each VPC derive from this range.

The /16 block is evenly split in eight, smaller /19 blocks, assigned to different areas of the GCP network: landing untrusted europe-west1, landing untrusted europe-west4, landing trusted europe-west1, landing untrusted europe-west4, development europe-west1, development europe-west4, production europe-west1, production europe-west4.

The first /24 range in every area is allocated for a default subnet, which can be removed or modified as needed.

Spoke VPCs also define and reserve three "special" CIDR ranges, derived from the respective /19, dedicated to

This is a summary of the subnets allocated by default in this setup:

name description CIDR
landing-trusted-default-ew1 Trusted landing subnet - europe-west1 10.128.64.0/24
landing-trusted-default-ew4 Trusted landing subnet - europe-west4 10.128.96.0/24
landing-untrusted-default-ew1 Untrusted landing subnet - europe-west1 10.128.0.0/24
landing-untrusted-default-ew4 Untrusted landing subnet - europe-west4 10.128.32.0/24
dev-default-ew1 Dev spoke subnet - europe-west1 10.128.128.0/24
dev-default-ew1 (PSA MySQL) PSA subnet for MySQL in dev spoke - europe-west1 10.128.157.0/24
dev-default-ew1 (PSA SQL Server) PSA subnet for Postgres in dev spoke - europe-west1 10.128.158.0/24
dev-default-ew1 (L7 ILB) L7 ILB subnet for dev spoke - europe-west1 10.128.92.0/24
dev-default-ew4 Dev spoke subnet - europe-west4 10.128.160.0/24
dev-default-ew4 (PSA MySQL) PSA subnet for MySQL in dev spoke - europe-west4 10.128.189.0/24
dev-default-ew4 (PSA SQL Server) PSA subnet for Postgres in dev spoke - europe-west4 10.128.190.0/24
dev-default-ew4 (L7 ILB) L7 ILB subnet for dev spoke - europe-west4 10.128.93.0/24
prod-default-ew1 Prod spoke subnet - europe-west1 10.128.192.0/24
prod-default-ew1 (PSA MySQL) PSA subnet for MySQL in prod spoke - europe-west1 10.128.221.0/24
prod-default-ew1 (PSA SQL Server) PSA subnet for Postgres in prod spoke - europe-west1 10.128.253.0/24
prod-default-ew1 (L7 ILB) L7 ILB subnet for prod spoke - europe-west1 10.128.60.0/24
prod-default-ew4 Prod spoke subnet - europe-west4 10.128.224.0/24
prod-default-ew4 (PSA MySQL) PSA subnet for MySQL in prod spoke - europe-west4 10.128.222.0/24
prod-default-ew4 (PSA SQL Server) PSA subnet for Postgres in prod spoke - europe-west4 10.128.254.0/24
prod-default-ew4 (L7 ILB) L7 ILB subnet for prod spoke - europe-west4 10.128.61.0/24

These subnets are advertised to on-premises as a whole /16 range (10.128.0.0/16).

Routes in GCP are either automatically created (for example, when a subnet is added to a VPC), manually created via static routes, dynamically exchanged through VPC peerings, or dynamically programmed by Cloud Routers when a BGP session is established. BGP sessions can be configured to advertise VPC ranges, and/or custom ranges via custom advertisements.

In this setup:

  • routes between multiple subnets within the same VPC are automatically exchanged by GCP
  • the spokes and the trusted landing VPC exchange routes through VPC peerings
  • on-premises is connected to the trusted landing VPC and it dynamically exchanges BGP routes with GCP (with the trusted VPC) using HA VPN
  • for cross-environment (spokes) communications, and for connections to on-premises and to the Internet, the spokes leverage some default tagged routes that send the traffic of each region (whose machines are identified by a dedicated network tag, e.g. ew1) to a corresponding regional NVA in the trusted VPC, through an ILB (whose VIP is set as the route next-hop)
  • the spokes are configured with backup default routes, so if the NVAs in the same region become unavailable, more routes to the NVAs in the other region are already available. Current routes are not able to understand if the next-hop ILBs become unhealthy. As such, in case of a regional failure, users will need to manually withdraw the primary default routes, so the secondaries will take over
  • the NVAs are configured with static routes that allow the communication with on-premises and between the GCP resources (including the cross-environment communication)

The Cloud Routers (connected to the VPN gateways in the trusted VPC) are configured to exclude the default advertisement of VPC ranges and they only advertise their respective aggregate ranges, via custom advertisements. This greatly simplifies the routing configuration and avoids quota or limit issues, by keeping the number of routes small, instead of making it proportional to the subnets and to the secondary ranges in the VPCs.

Internet egress

In this setup, Internet egress is realized through Cloud NAT, deployed in the untrusted landing VPC. This allows instances in all other VPCs to reach the Internet, passing through the NVAs (being the public Internet considered untrusted).

Several other scenarios are possible, with various degrees of complexity:

  • deploy Cloud NAT in every VPC
  • add forwarding proxies, with optional URL filters
  • send Internet traffic to on-premises, so the existing egress infrastructure can be leveraged

Future pluggable modules will allow users to easily experiment with the above scenarios.

VPC and Hierarchical Firewall

The GCP Firewall is a stateful, distributed feature that allows the creation of L4 policies, either via VPC-level rules or -more recently- via hierarchical policies, applied on the resource hierarchy (organization, folders).

The current setup adopts both firewall types. Hierarchical firewall rules are applied in the networking folder for common ingress rules (egress is open by default): for example, it allows the health checks and the IAP forwarders traffic to reach the VMs.

Rules and policies are defined in simple YAML files, described below.

DNS

DNS goes hand in hand with networking, especially on GCP where Cloud DNS zones and policies are associated at the VPC level. This setup implements both DNS flows:

  • on-prem to cloud via private zones for cloud-managed domains, and an inbound policy used as forwarding target or via delegation (requires some extra configuration) from on-prem DNS resolvers
  • cloud to on-prem via forwarding zones for the on-prem managed domains

DNS configuration is further centralized by leveraging peering zones, so that

  • the hub/landing Cloud DNS hosts configurations for on-prem forwarding, Google API domains, and the top-level private zone/s (e.g. gcp.example.com)
  • the spokes Cloud DNS host configurations for the environment-specific domains (e.g. prod.gcp.example.com), which are bound to the hub/landing leveraging cross-project binding; a peering zone for the . (root) zone is then created on each spoke, delegating all DNS resolution to hub/landing.
  • Private Google Access is enabled for a selection of the supported domains, namely
    • private.googleapis.com
    • restricted.googleapis.com
    • gcr.io
    • packages.cloud.google.com
    • pkg.dev
    • pki.goog

To complete the configuration, the 35.199.192.0/19 range should be routed to the VPN tunnels from on-premises, and the following names should be configured for DNS forwarding to cloud:

  • private.googleapis.com
  • restricted.googleapis.com
  • gcp.example.com (used as a placeholder)

In GCP, a forwarding zone in the landing project is configured to forward queries to the placeholder domain onprem.example.com to on-premises.

This configuration is battle-tested, and flexible enough to lend itself to simple modifications without subverting its design.

How to run this stage

This stage is meant to be executed after the resman stage has run. It leverages the automation service account and the storage bucket created there, and additional resources configured in the bootstrap stage.

It's possible to run this stage in isolation, but that's outside of the scope of this document. Please, refer to the previous stages for the environment requirements.

Before running this stage, you need to make sure you have the correct credentials and permissions. You'll also need identify the module variables and make sure you assign them the values that match your configuration.

Providers configuration

The default way of making sure you have the right permissions, is to use the identity of the service account pre-created for this stage, during the resource management stage, and that you are a member of the group that can impersonate it via provider-level configuration (gcp-devops or organization-admins).

To simplify the setup, the previous stage pre-configures a valid providers file in its output and optionally writes it to a local file if the outputs_location variable is set to a valid path.

If you have set a valid value for outputs_location in the bootstrap stage, simply link the relevant providers.tf file from this stage folder in the path you selected:

# `outputs_location` is set to `~/fast-config`
ln -s ~/fast-config/providers/02-networking-providers.tf .

If you have not configured outputs_location in bootstrap, you can derive the providers file from that stage outputs:

cd ../01-resman
terraform output -json providers | jq -r '.["02-networking"]' \
  > ../02-networking-nva/providers.tf

Variable configuration

There are two broad sets of variables you will need to fill in:

  • variables shared by other stages (org id, billing account id, etc.), or derived from a resource managed by a different stage (folder id, automation project id, etc.)
  • variables specific to resources managed by this stage

To avoid the tedious job of filling in the first group of variables with values derived from other stages outputs, the same mechanism used above for the provider configuration can be used to leverage pre-configured .tfvars files.

If you have set a valid value for outputs_location in the bootstrap and in the resman stage, simply link the relevant *.auto.tfvars.json files from this stage's folder in the path you specified. The * above is set to the name of the stage that produced it, except for globals.auto.tfvars.json which is also generated by the bootstrap stage, containing global values compiled manually for the bootstrap stage. For this stage, link the following files:

# `outputs_location` is set to `~/fast-config`
ln -s ~/fast-config/tfvars/globals.auto.tfvars.json .
ln -s ~/fast-config/tfvars/00-bootstrap.auto.tfvars.json .
ln -s ~/fast-config/tfvars/01-resman.auto.tfvars.json .

A second set of variables is specific to this stage, they are all optional so if you need to customize them, create an extra terraform.tfvars file.

Please, refer to the variables table below for a map of the variable origins, and use the sections below to understand how to adapt this stage to your networking configuration.

VPCs

VPCs are defined in separate files, one for landing (trusted and untrusted), one for prod and one for dev.

These files contain different resources:

  • project (projects): the "host projects" containing the VPCs and enabling the required APIs.
  • VPCs (net-vpc): manage the subnets, the explicit routes for {private,restricted}.googleapis.com and the DNS inbound policy (for the trusted landing VPC). Subnets are created leveraging "resource factories": the configuration is separated from the module that implements it, and stored in a well-structured file. To add a new subnet, simply create a new file in the data_folder directory defined in the module, following the examples found in the Fabric net-vpc documentation. Sample subnets are shipped in data/subnets and can be easily customized to fit users' needs.

Subnets for L7 ILBs are handled differently, and defined in variable l7ilb_subnets, while ranges for PSA are configured by variable psa_ranges - such variables are consumed by spoke VPCs.

  • Cloud NAT (net-cloudnat) (in the untrusted landing VPC only): it manages the networking infrastructure required to enable the Internet egress.

VPNs

The connectivity between on-premises and GCP (the trusted landing VPC) is implemented with Cloud HA VPN (net-vpn) and defined in vpn-onprem.tf. The file implements a single logical connection between on-premises and the trusted landing VPC, both in europe-west1 and europe-west4. The relevant parameters for its configuration are found in the variable vpn_onprem_configs.

Routing and BGP

Each VPC network (net-vpc) manages a separate routing table, which can define static routes (e.g. to private.googleapis.com) and receives dynamic routes through VPC peering and BGP sessions established with the neighbor networks (e.g. the trusted landing VPC receives routes from on-premises, and the spokes receive RFC1918 from the trusted landing VPC).

Static routes are defined in vpc-*.tf files in the routes section of each net-vpc module.

BGP sessions for trusted landing to on-premises are configured through the variable vpn_onprem_configs.

Firewall

VPC firewall rules (net-vpc-firewall) are defined per-vpc on each vpc-*.tf file and leverage a resource factory to massively create rules. To add a new firewall rule, create a new file or edit an existing one in the data_folder directory defined in the module net-vpc-firewall, following the examples of the "Rules factory" section of the module documentation. Sample firewall rules are shipped in data/firewall-rules/landing-untrusted and in data/firewall-rules/landing-trusted, and can be easily customized.

Hierarchical firewall policies (folder) are defined in main.tf, and managed through a policy factory implemented by the folder module, which applies the defined hierarchical to the Networking folder, which contains all the core networking infrastructure. Policies are defined in the rules_file file - to define a new one simply use the instructions found on "Firewall policy factory". Sample hierarchical firewall policies are shipped in data/hierarchical-policy-rules.yaml and can be easily customized.

DNS architecture

The DNS (dns) infrastructure is defined in [dns-*.tf] files.

Cloud DNS manages onprem forwarding, the main GCP zone (in this example gcp.example.com) and environment-specific zones (i.e. dev.gcp.example.com and prod.gcp.example.com).

Cloud environment

The root DNS zone defined in the landing project acts as the source of truth for DNS within the Cloud environment. The resources defined in the spoke VPCs consume the landing DNS infrastructure through DNS peering (e.g. prod-landing-root-dns-peering). The spokes can optionally define private zones (e.g. prod-dns-private-zone). Granting visibility both to the trusted and untrusted landing VPCs ensures that the whole cloud environment can query such zones.

Cloud to on-premises

Leveraging the forwarding zone defined in the landing project (e.g. onprem-example-dns-forwarding and reverse-10-dns-forwarding), the cloud environment can resolve in-addr.arpa. and onprem.example.com. using the on-premise DNS infrastructure. On-premise resolver IPs are set in the variable dns.onprem.

DNS queries sent to the on-premise infrastructure come from the 35.199.192.0/19 source range.

On-premises to cloud

The Inbound DNS Policy defined in the trusted landing VPC module (landing.tf) automatically reserves the first available IP address on each subnet (typically the third one in a CIDR) to expose the Cloud DNS service, so that it can be consumed from outside of GCP.

Private Google Access

Private Google Access (or PGA) is configured in this environment. It enables VMs and on-premise systems to consume Google APIs from within the Google network.

For PGA to work:

  • Private Google Access should be enabled on the subnet.
    Subnets created using the net-vpc module are PGA-enabled by default.

  • 199.36.153.4/30 (restricted.googleapis.com) and 199.36.153.8/30 (private.googleapis.com) should be routed from on-premises to the trusted landing VPC, and from there to the default-internet-gateway.
    The vpn_onprem_configs variable contains the ranges advertised from GCP to on-premises. Furthermore, the trusted landing VPC (e.g. see landing-trusted-vpc in landing.tf) has explicit routes to send traffic destined to restricted and private - googleapis.com to the Internet gateway (which works for Google APIs only, and not for the whole Internet, since Cloud NAT is not configured in the trusted landing VPC).

  • On-premises, a private DNS zone for googleapis.com should be created and configured per this article. Its configuration can be copied from the module googleapis-private-zone in dns-landing.tf

Preliminar activities

Before running terraform apply, make sure to adapt variables.tf to your needs, to update the variable values using a new terraform.tfvars file, and to update the references to the regions in the whole directory, in order to match your preferences (e.g. europe-west1 or ew1).

If you're not using other FAST stages, you'll also need to create a providers.tf file to configure the GCS backend and the service account to use to run the deployment.

You're now ready to run terraform init and terraform apply.

Post-deployment activities

  • On-premise routers should be configured to advertise all relevant CIDRs to the GCP environments. To avoid hitting GCP quotas, we recommend aggregating routes as much as possible
  • On-premise routers should accept BGP sessions from their cloud peers
  • On-premise DNS servers should have forward zones configured, in order to resolve GCP-managed domains

Customizations

Adding an environment

To create a new environment (e.g. staging), a few changes are required:

Create a spoke-staging.tf file by copying spoke-prod.tf file. Adapt the new file by replacing the value "prod" with the value "staging". Running diff spoke-dev.tf spoke-prod.tf can help to see how environment files differ.

The new VPC requires a set of dedicated CIDRs, one per region, added to variable custom_adv (for example as spoke_staging_ew1 and spoke_staging_ew4).

custom_adv is a map that "resolves" CIDR names to the actual addresses, and will be used later to configure routing.

Variables managing L7 Internal Load Balancers (l7ilb_subnets) and Private Service Access (psa_ranges) should also be adapted, and subnets and firewall rules for the new spoke should be added, as described above.

VPC network peering connectivity to the trusted landing VPC is managed by the vpc-peering-*.tf files. Copy vpc-peering-prod.tf to vpc-peering-staging.tf and replace "prod" with "staging", where relevant.

Configure the NVAs deployed or update the sample NVA config file making sure they support the new subnets.

DNS configurations are centralised in the dns-*.tf files. Spokes delegate DNS resolution to Landing through DNS peering, and optionally define a private zone (e.g. dev.gcp.example.com) which the landing peers to. To configure DNS for a new environment, copy one of the other environments DNS files e.g. (dns-dev.tf) into a new dns-*.tf file suffixed with the environment name (e.g. dns-staging.tf), and update its content accordingly. Don't forget to add a peering zone from the landing to the newly created environment private zone.

Files

name description modules resources
dns-dev.tf Development spoke DNS zones and peerings setup. dns
dns-landing.tf Landing DNS zones and peerings setup. dns
dns-prod.tf Production spoke DNS zones and peerings setup. dns
landing.tf Landing VPC and related resources. net-cloudnat · net-vpc · net-vpc-firewall · project
main.tf Networking folder and hierarchical policy. folder
monitoring.tf Network monitoring dashboards. google_monitoring_dashboard
nva.tf None compute-mig · compute-vm · simple-nva
outputs.tf Module outputs. google_storage_bucket_object · local_file
spoke-dev.tf Dev spoke VPC and related resources. net-vpc · net-vpc-firewall · net-vpc-peering · project google_project_iam_binding
spoke-prod.tf Production spoke VPC and related resources. net-vpc · net-vpc-firewall · net-vpc-peering · project google_project_iam_binding
test-resources.tf temporary instances for testing compute-vm
variables.tf Module variables.
vpn-onprem.tf VPN between landing and onprem. net-vpn-ha

Variables

name description type required default producer
automation Automation resources created by the bootstrap stage. object({…}) ✓ 00-bootstrap
billing_account Billing account id and organization id ('nnnnnnnn' or null). object({…}) ✓ 00-bootstrap
folder_ids Folders to be used for the networking resources in folders/nnnnnnnnnnn format. If null, folder will be created. object({…}) ✓ 01-resman
organization Organization details. object({…}) ✓ 00-bootstrap
prefix Prefix used for resources that need unique names. Use 9 characters or less. string ✓ 00-bootstrap
custom_adv Custom advertisement definitions in name => range format. map(string) {…}
custom_roles Custom roles defined at the org level, in key => id format. object({…}) null 00-bootstrap
data_dir Relative path for the folder storing configuration data for network resources. string "data"
dns Onprem DNS resolvers map(list(string)) {…}
l7ilb_subnets Subnets used for L7 ILBs. map(list(object({…}))) {…}
onprem_cidr Onprem addresses in name => range format. map(string) {…}
outputs_location Path where providers and tfvars files for the following stages are written. Leave empty to disable. string null
psa_ranges IP ranges used for Private Service Access (e.g. CloudSQL). object({…}) null
region_trigram Short names for GCP regions. map(string) {…}
router_configs Configurations for CRs and onprem routers. map(object({…})) {…}
service_accounts Automation service accounts in name => email format. object({…}) null 01-resman
vpn_onprem_configs VPN gateway configuration for onprem interconnection. map(object({…})) {…}

Outputs

name description sensitive consumers
host_project_ids Network project ids.
host_project_numbers Network project numbers.
shared_vpc_self_links Shared VPC host projects.
tfvars Terraform variables file for the following stages. ✓
vpn_gateway_endpoints External IP Addresses for the GCP VPN gateways.