host project

Related topics

• host project is part of Shared VPC From the official documentation: “When you use Shared VPC, you designate a project as a *Shared VPC host project* and attach one or more *service projects* to it.”
• service project depends on host project From the official documentation: “A service project must attach to a host project before its Service Project Admins can use the Shared VPC.”
• Shared VPC depends on host project From the official documentation: “Each Shared VPC network is defined and owned by a centralized *host project*, and can be used by one or more *service projects*.”
• host project works with service project From the official documentation: “You can use a single VPC network in a host project to connect resources from multiple service projects.”
• host project is an alternative to service project From the official documentation: “If your organization uses Shared VPC, you can set up a Serverless VPC Access connector in either the service project or the host project.”
• Private Google Access configures host project From the official documentation: “If you plan to use **Private IP environments**, then [enable Private Google Access](/vpc/docs/configure-private-google-access#enabling-pga) for the subnet in the host project.”
• Shared VPC is part of host project From the official documentation: “The Shared VPC host project is the project which contains the Shared VPC network.”
• Private Google Access is an alternative to Private Service Connect From the official documentation: “Private Service Connect to access Google APIs is an alternative to using Private Google Access or the public domain names for Google APIs.”
• service project is part of Shared VPC From the official documentation: “When you use Shared VPC, you designate a project as a *Shared VPC host project* and attach one or more *service projects* to it.”
• Dataflow works with Shared VPC From the official documentation: “The following error occurs when you run a Dataflow job on a Shared VPC network:”
• Dataflow works with GKE From the official documentation: “Route Dataflow events to GKE”
• Dataflow depends on Private Google Access From the official documentation: “Workflow failed. Causes: Subnetwork SUBNETWORK on project PROJECT_ID network NETWORK in region REGION does not have Private Google Access, which is required for usage of private IP addresses by the Dataflow workers.”
• Dataflow works with Private Google Access From the official documentation: “Enable Private Google Access and specify one of the following options in your Dataflow job:”
• GKE works with Private Google Access From the official documentation: “When a cluster or node pool is created or updated with the `--enable-private-nodes` flag, GKE automatically enables Private Google Access on this subnet.”
• GKE works with Private Service Connect From the official documentation: “This page provides an overview of Private Service Connect in Google Kubernetes Engine (GKE) clusters.”
• GKE works with Shared VPC From the official documentation: “For networking, GKE clusters are deployed in a Shared VPC that's created as part of the enterprise foundation blueprint.”
• Private Google Access configures Dataflow From the official documentation: “However, to allow Dataflow workers with private IP addresses to access the external IP addresses that Google Cloud APIs and services use, you must also manually enable Private Google Access for the subnet.”
• 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.”
• Shared VPC depends on service project From the official documentation: “Shared VPC requires that you designate a *host project* to which networks and subnetworks belong and a *service project*, which is attached to the host project.”