This page describes how to connect additional networks to your volumes.
Google Cloud NetApp Volumes uses private service access to host your volumes. Volumes are provisioned on a tenant VPC within a service-internal project. The tenant VPC is connected to your project VPC using VPC peering. Therefore, only clients connected to your project VPC can access the volumes. If you want to grant access to the volumes to clients on different networks, you have to establish additional network connections.
The following are the connectivity options:
Shared VPCs: a common approach is to put both NetApp Volumes and all client VMs on the same shared VPC, while keeping the VMs in different service projects for workload isolation and billing purposes.
VPN connection: if you connect an additional VPC to your project VPC using VPN instead of VPC peering, you can configure transitive routing.
VPC peering: if you connect additional VPCs to your project's VPC using peering, clients on those VPCs can't connect to your volumes as VPC peering doesn't provide transitive routing. However, you can establish direct peerings between these additional VPCs and the tenant VPC. For more information, see Connect additional networks with manual peering.
Interconnects: if you connect additional networks to your project VPC using interconnects, you can configure transitive routing.
Connect additional networks with manual peering
NetApp Volumes establishes connectivity by creating a private service access tenant project and network, which is then connected with your specified project network by VPC peering. To enable clients in other networks to access the same volumes, you can peer additional VPCs from your projects to this tenant network.
For any requests to peer an additional VPC with a NetApp Volumes tenant project, contact Google Cloud Customer Care.
Before you proceed, we recommend that you review the VPC peering documentation to learn about VPC peering limitations, limits, and billing.