VPC spoke

Related topics

• VPC spoke is part of Network Connectivity Center From the official documentation: “To create a Network Connectivity Center (NCC) VPC spoke, enable the `networkconnectivity` API:”
• hybrid spoke works with VPC spoke From the official documentation: “Mesh topology also supports high scale network connectivity between VPC spokes and hybrid spokes.”
• hub works with VPC spoke From the official documentation: “To connect multiple VPC networks within a given project, connect a VPC network to a spoke, and connect it to a hub.”
• VPC network works with VPC spoke From the official documentation: “To connect multiple VPC networks to each other, add each network to the same hub as a VPC spoke.”
• VPC spoke is part of hub From the official documentation: “After a VPC network is added to a NCC hub as a VPC spoke, new Private Service Connect endpoints are also propagated, unless the endpoint's subnet is excluded from export.”
• VPC spoke depends on hub From the official documentation: “When you create a spoke, you must associate it with a hub.”
• VPC spoke depends on hybrid spoke From the official documentation: “VPC spokes can connect to on-premises networks by using hybrid spokes located in other routing VPC networks.”
• Router appliance is part of Network Connectivity Center From the official documentation: “Router appliance within Network Connectivity Center”
• hub is part of Network Connectivity Center From the official documentation: “Quotas that apply to network routes for Cloud Router also apply to routes for NCC hubs and spokes.”
• internal passthrough Network Load Balancer works with Network Connectivity Center From the official documentation: “NCC supports a next hop internal passthrough Network Load Balancer in a VPC spoke subject to [NCC requirements for connectivity](/network-connectivity/docs/network-connectivity-center/concepts/static-routes-overview).”
• internal passthrough Network Load Balancer works with Shared VPC From the official documentation: “The following table summarizes the component requirements for internal passthrough Network Load Balancers used with Shared VPC networks.”
• Network Connectivity Center works with Private Service Connect From the official documentation: “Private Service Connect consumer access points are reachable over Network Connectivity Center.”
• spoke is part of hub From the official documentation: “Create spokes and add the spokes to the hub.”
• spoke is part of Network Connectivity Center From the official documentation: “Then you create a NCC *spoke* to represent each connectivity resource.”
• hub works with hybrid spoke From the official documentation: “Connect the VLAN attachment or tunnel as a hybrid spoke to join the NCC hub that you created in step 1.”
• hub works with Router appliance From the official documentation: “Quotas that apply to network routes for Cloud Router also apply to routes for Router appliance spokes attached to NCC hubs.”
• hybrid spoke is part of hub From the official documentation: “Your NCC hub must have only one [routing VPC network](/network-connectivity/docs/network-connectivity-center/concepts/dynamic-route-exchange-with-vpc-spokes#routing-vpc) that contains all of its hybrid spokes.”
• internal passthrough Network Load Balancer works with Private Service Connect From the official documentation: “You can expose your GKE Services by using an internal passthrough Network Load Balancer and [service attachments](/vpc/docs/private-service-connect#service-attachments), and consume these services by using an [endpoint](/vpc/docs/private-service-connect#endpoints) from other…”
• internal passthrough Network Load Balancer depends on VPC network From the official documentation: “By default, an internal passthrough Network Load Balancer is available only from within the VPC network that hosts it.”
• Network Connectivity Center works with Router appliance From the official documentation: “Router appliance is an alternative way of enabling connectivity between sites outside of Google Cloud through a NCC hub.”
• Network Connectivity Center is an alternative to Shared VPC From the official documentation: “Hub-and-spoke [Shared VPC](/vpc/docs/shared-vpc) topology or [Network Connectivity Center](/network-connectivity/docs/network-connectivity-center) architectures that minimize public exposure”
• Network Connectivity Center works with VPC network From the official documentation: “You can use Network Connectivity Center (NCC) to connect VPC networks by using a hub and spoke connectivity model.”
• Private Service Connect works with Shared VPC From the official documentation: “Private Service Connect resources can be deployed in standalone VPC networks or Shared VPC networks.”
• Private Service Connect is an alternative to VPC network From the official documentation: “In Managed Airflow (Gen 2), you can create environments that [use Private Service Connect](/composer/docs/composer-2/configure-private-service-connect) instead of VPC networks.”
• Router appliance depends on Network Connectivity Center From the official documentation: “*Router appliance requires NCC to operate.*”
• Router appliance works with Shared VPC From the official documentation: “Router appliance is only supported in the Shared VPC model when deployed in the host project.”
• Shared VPC is an alternative to VPC network From the official documentation: “The VLAN attachment or Cloud VPN tunnel must terminate in the same VPC network (or Shared VPC network) as the endpoint.”
• spoke depends on hub From the official documentation: “First, you create a hub. Later, you attach spokes to this hub.”