[[["易于理解","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-08-12。"],[],[],null,["# Producer VPC spokes\n\nThis page provides an overview of producer Virtual Private Cloud (VPC) spokes in Network Connectivity Center.\n\n\u003cbr /\u003e\n\nIntroduction\n------------\n\nSome service providers let you access managed services by using a\n[VPC Network Peering](/vpc/docs/using-vpc-peering) connection between their\nVPC network and your VPC network, such as services\noffered through [private services access](/vpc/docs/private-services-access).\nIn these cases, the producer VPC network is in a producer-owned\nproject that you are unable to access directly.\n\nIf you have a VPC network that consumes a service from a producer\nnetwork in another project through VPC Network Peering, you can use a\nNetwork Connectivity Center *producer VPC spoke* to make the service reachable by other\nnetworks.\n\nHow it works\n------------\n\nWhen you create a producer VPC spoke, you provide the following:\n\n- The existing VPC spoke of your consumer network that is peered with the producer network.\n- The name of the peering connection.\n\nThen, Network Connectivity Center uses that information to identify the\nVPC network of the service producer and add a corresponding\nproducer VPC spoke to a hub in your project.\n\nAfter the producer VPC spoke is part of the hub, its subnet routes\nare exported and the other spokes on that hub can access its services.\n\n### Example configuration\n\nThe example configuration in the following diagram includes:\n\n- A *Service producer network* that is a producer VPC spoke on the hub.\n- A *Peered consumer network* that is a VPC spoke on the hub.\n- Additional networks, *Network 3* and *Network 4*, that are also VPC spokes on the hub.\n\nAll of the networks attached to the hub as VPC spokes can access\nthe services in the producer network:\n\n- The peered consumer network continues to access services by using the subnet routes exported from the service producer network through the existing VPC Network Peering connection.\n- Network 3 and Network 4 have the same access to services in the producer network through Network Connectivity Center. The subnet routes from the service producer network are exported to the hub and advertised to the VPC spokes associated with Networks 3 and 4.\n\n[](/static/network-connectivity/docs/network-connectivity-center/images/producer-vpc-spokes.svg) Network Connectivity Center producer VPC spoke (click to enlarge).\n\nSupported services\n------------------\n\nFor a list of supported services, see\n[Supported services for producer VPC spokes](/network-connectivity/docs/network-connectivity-center/concepts/producer-vpc-spokes-supported-services).\n\nConsiderations\n--------------\n\nThe following sections describe considerations for using producer\nVPC spokes.\n\n### Shared properties with VPC spokes\n\nProducer VPC spokes are a type of VPC spoke,\nwhich means they inherit most of the properties of\nVPC spokes described in the [VPC\nspokes overview](/network-connectivity/docs/network-connectivity-center/concepts/vpc-spokes-overview). For example,\nboth spoke types do the following:\n\n- Connect a VPC network to a Network Connectivity Center hub.\n- Export subnet routes to the Network Connectivity Center hub, which advertises those routes to other VPC spokes and [routing VPC networks](/network-connectivity/docs/network-connectivity-center/concepts/dynamic-route-exchange-with-vpc-spokes#routing-vpc). This includes any new subnets added to the producer VPC spoke, which means that other spokes can access newly provisioned services from a producer VPC spoke.\n- Import dynamic routes from the Network Connectivity Center hub routing table, providing connectivity to hybrid spokes. The hub [topology](/network-connectivity/docs/network-connectivity-center/concepts/vpc-spokes-overview#preset-topologies) must also support dynamic route exchange.\n- Limit which subnets are exported by using [export filters](/network-connectivity/docs/network-connectivity-center/concepts/vpc-spokes-overview#vpc-connectivity-with-export-filters).\n- Use the same [Network Connectivity Center quotas and limits](/network-connectivity/docs/network-connectivity-center/quotas), including:\n\n - Number of active VPC spokes per hub\n - Number of subnet routes per hub route table\n\n If adding a producer VPC spoke could result in the hub\n exceeding the limit of either of the preceding quotas, Network Connectivity Center\n prohibits you from adding the producer VPC spoke. To reduce\n the usage of the *number of subnet routes per hub route table* quota, you\n can use export filters to limit which of the subnets in the producer\n VPC spoke are exported.\n\nThe [limitations](/network-connectivity/docs/network-connectivity-center/concepts/vpc-spokes-overview#limitations) of\nVPC spokes also apply to producer VPC spokes.\n\n### Properties unique to producer VPC spokes\n\nProducer VPC spokes have the following unique properties and\nrequirements:\n\n### Avoid overlap with allocated IP ranges\n\nIf you want to create a producer VPC spoke for a\nsupported service offered through private services access,\nconsider the following:\n\n- Network Connectivity Center does not check for overlaps with allocated IP ranges. Ensure that the IP address ranges of the VPC spokes on your hub don't overlap with an allocated IP range configured for private services access.\n- If your VPC spokes overlap with allocated IP ranges, private services access might not be able to create new resources when needed and you'll get an error. To resolve this, expand or modify the allocated IP range.\n\nFor more information, see\n[Allocated IP address ranges for services](/vpc/docs/configure-private-services-access#allocating-range).\n\nWhat's next\n-----------\n\n- [Create a producer VPC spoke](/network-connectivity/docs/network-connectivity-center/how-to/create-producer-vpc-spoke)\n- [Troubleshoot Network Connectivity Center](/network-connectivity/docs/network-connectivity-center/support/troubleshooting)\n- [Get details about API and `gcloud` commands](/network-connectivity/docs/network-connectivity-center/apis)"]]
