[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[],[],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."]]
