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*.”
• VPC network is part of host project From the official documentation: “The host project contains two VPC networks `VPC1` and `VPC2`.”
• 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.”
• service perimeter secures host project From the official documentation: “The service perimeter `perimeter-1` protects the entire host project and service projects.”
• 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.”
• service perimeter is part of VPC Service Controls From the official documentation: “Learn how to set up a service perimeter using VPC Service Controls.”
• subnet is part of VPC network From the official documentation: “When you delete a VPC, its subnets are also deleted.”
• 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.”
• Apigee works with Shared VPC From the official documentation: “If your project uses Shared Virtual Private Cloud (VPC) networking, you can select the shared network that will be used to peer with Apigee.”
• 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.”
• Shared VPC works with VPC Service Controls From the official documentation: “If you use both Shared VPC and VPC Service Controls, the host project that contains the network and the service project that contains the Managed Lustre instance must both be inside the same perimeter.”
• Apigee works with Private Service Connect From the official documentation: “Network connectivity issues between Apigee and a southbound target service connected by Private Service Connect.”
• Cloud Interconnect works with Private Google Access From the official documentation: “With Private Google Access, your on-premises or Google Cloud VMware Engine hosts connect to Google Cloud APIs through a Cloud VPN tunnel or Cloud Interconnect.”
• Private Service Connect works with VPC Service Controls From the official documentation: “VPC Service Controls that use Private Service Connect”
• VPC Service Controls configures service perimeter From the official documentation: “VPC Service Controls lets you set up a service perimeter to guard against data exfiltration.”
• Apigee depends on VPC network From the official documentation: “Ensure there is an available VPC network in the Google Cloud project you will use to provision Apigee.”
• Cloud Interconnect works with VPC network From the official documentation: “Connects to on-premises networks by using Cloud VPN tunnels and VLAN attachments for Cloud Interconnect.”
• Private Google Access configures subnet From the official documentation: “You enable Private Google Access on a subnet by subnet basis; it's a setting for subnets in a VPC network.”
• Apigee works with VPC Service Controls From the official documentation: “Apigee integrations with VPC Service Controls have the following limitations:”
• Cloud Interconnect works with Private Service Connect From the official documentation: “Clients in networks that are connected to Google Cloud with VLAN attachments for Cloud Interconnect or Cloud VPN tunnels can reach Private Service Connect endpoints.”
• Cloud Interconnect works with Shared VPC From the official documentation: “You can extend one or more of your existing security zones to Google Cloud by provisioning Shared VPC on Google Cloud and connecting it to the existing zone by using Cloud VPN or Cloud Interconnect.”
• Cloud Interconnect works with VPC Service Controls From the official documentation: “VPC Service Controls works with either Cloud Interconnect or Cloud VPN to provide additional security for your clusters.”
• 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.”
• GKE depends on VPC network From the official documentation: “A subnet is required in your VPC network to provide connectivity to your GKE nodes.”
• 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.”
• service perimeter secures service project From the official documentation: “The service perimeter `perimeter-1` protects the entire host project and service projects.”
• service perimeter works with VPC network From the official documentation: “For information about VPC networks limitations when you use VPC networks in service perimeters, see [VPC network limitations](/vpc-service-controls/docs/vpc-perimeters-management#limitations).”
• service perimeter secures VPC network From the official documentation: “This perimeter protects the VPC network `VPC1` and the service project `service-project-1`.”
• 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.”
• 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.”
• VPC Service Controls secures GKE From the official documentation: “The Kubernetes Engine API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”