Stay organized with collections
Save and categorize content based on your preferences.
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.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Connect additional networks\n\nThis page describes how to connect additional networks to your volumes.\n\nGoogle Cloud NetApp Volumes uses [private service access](/netapp/volumes/docs/get-started/configure-access/networking) to host your volumes. Volumes are provisioned on a tenant\nVPC within a service-internal project. The tenant\nVPC is connected to your project VPC using\nVPC peering. Therefore, only clients connected to your project\nVPC can access the volumes. If you want to grant access to the\nvolumes to clients on different networks, you have to establish additional\nnetwork connections.\n\nThe following are the connectivity options:\n\n- **Shared VPCs**: a common approach is to put both\n NetApp Volumes and all client VMs on the same shared\n VPC, while keeping the VMs in different service projects for\n workload isolation and billing purposes.\n\n- **VPN connection**: if you connect an additional VPC to your\n project VPC using VPN instead of VPC peering,\n you can configure transitive routing.\n\n- **VPC peering** : if you connect additional VPCs to your\n project's VPC using peering, clients on those\n VPCs can't connect to your volumes as [VPC\n peering doesn't provide transitive routing](/vpc/docs/vpc-peering#spec-general).\n However, you can establish direct peerings between these additional\n VPCs and the tenant VPC. For more information,\n see [Connect additional networks with manual peering](#connect_additional_networks_with_manual_peering).\n\n- **Interconnects**: if you connect additional networks to your project\n VPC using interconnects, you can configure transitive routing.\n\nConnect additional networks with manual peering\n-----------------------------------------------\n\nNetApp Volumes establishes connectivity by creating a\nprivate service access tenant project and network, which is then connected\nwith your specified project network by VPC peering. To enable\nclients in other networks to access the same volumes, you can peer additional\nVPCs from your projects to this tenant network.\n\nFor any requests to peer an additional VPC with a\nNetApp Volumes tenant project, contact [Google Cloud Customer Care](https://cloud.google.com/support-hub/).\n\nBefore you proceed, we recommend that you review the\n[VPC peering](/vpc/docs/vpc-peering) documentation to learn about\nVPC peering limitations, limits, and billing."]]
