Shared VPC

Related topics

• 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 is an alternative to VPC Network Peering From the official documentation: “We recommend using Shared VPC over using VPC Network Peering because Shared VPC is easier to configure and scale.”
• 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.”
• 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.”
• Cloud Service Mesh works with Shared VPC From the official documentation: “For a detailed explanation of how Shared VPC is supported with Cloud Service Mesh, see [Limitations](/service-mesh/v1.25/docs/service-routing/limitations).”
• Cloud Run works with Shared VPC From the official documentation: “To see which Cloud Run resources are using the Shared VPC network, run the following command:”
• Cloud VPN works with Shared VPC From the official documentation: “The Shared VPC network is connected by using [Cloud VPN](/network-connectivity/docs/vpn/concepts/overview) to an on-premises network.”
• 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*.”
• Shared VPC is an alternative to Virtual Private Cloud From the official documentation: “From the **Network** drop-down, select a VPC or a Shared VPC network.”
• Shared VPC works with VPC Network Peering From the official documentation: “You can use Shared VPC with clusters based on VPC Network Peering.”
• 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 Load Balancing works with Shared VPC From the official documentation: “Shared VPC can be used in conjunction with [Cloud Load Balancing](/load-balancing/docs/load-balancing-overview).”
• Cloud NAT works with Shared VPC From the official documentation: “You can deploy [Cloud NAT](/nat/docs) into the same Shared VPC host project network.”
• 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 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 is part of host project From the official documentation: “The Shared VPC host project is the project which contains the Shared VPC network.”
• 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.”
• Cloud Interconnect is an alternative to Cloud VPN From the official documentation: “Accessible by using hybrid connectivity (Cloud Interconnect or Cloud VPN).”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
• Cloud Logging works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh stores the dry-run results to Cloud Logging in the following labels:”
• Cloud Monitoring works with Cloud Service Mesh From the official documentation: “Mesh telemetry is no longer automatically ingested into Cloud Monitoring.”
• Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
• Cloud Run works with Cloud Service Mesh From the official documentation: “This section shows you how to troubleshoot common errors with Cloud Service Mesh and Cloud Run.”
• Cloud Service Mesh works with VPC Service Controls From the official documentation: “You can now use VPC Service Controls with Cloud Service Mesh.”
• Cloud Interconnect works with Cloud VPN From the official documentation: “You must enable high-availability (HA) VPN functionality when using Cloud Interconnect<br>with Cloud VPN.”
• Cloud Run is an alternative to GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
• Cloud VPN is an alternative to VPC Network Peering From the official documentation: “As a variation to the design, you can use Cloud VPN instead of VPC Network Peering.”
• Cloud Load Balancing works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh works with Cloud Load Balancing to provide a managed ingress experience.”
• Cloud Service Mesh works with VPC Network Peering From the official documentation: “Cloud Service Mesh supports [VPC Network Peering](/vpc/docs/vpc-peering) with the [service routing APIs](/service-mesh/docs/service-routing/service-routing-overview).”
• 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 Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• Cloud Service Mesh works with GKE From the official documentation: “# Set up a proxyless gRPC service mesh on GKE”
• Cloud VPN works with Virtual Private Cloud From the official documentation: “If you are connecting to a Virtual Private Cloud (VPC) network by using Cloud VPN, the Pod and Service CIDR blocks must not conflict with any CIDR blocks on your VPC network.”
• Cloud Interconnect works with Virtual Private Cloud From the official documentation: “By default, any VPC network can use Cloud Interconnect.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Service Mesh works with Compute Engine From the official documentation: “You can run applications on the following platforms and adopt them into a global service mesh that Cloud Service Mesh configures. | Feature | Supported | | --- | --- | | Compute Engine virtual machine (VM) instances | ✔ |”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• Private Service Connect depends on Cloud VPN From the official documentation: “Optional: [Configure Private Service Connect to let your Pods access Google Cloud APIs and services by using Cloud VPN](/vpc/docs/private-service-connect).”
• Private Service Connect works with VPC Service Controls From the official documentation: “VPC Service Controls that use Private Service Connect”
• Apigee works with Compute Engine From the official documentation: “| [Compute Engine](https://console.cloud.google.com/apis/library/compute.googleapis.com) | `compute.googleapis.com` | Used for managing your Apigee runtime. |”
• Cloud Load Balancing works with Cloud Monitoring From the official documentation: “Key performance and health metrics reported by Cloud Monitoring for Cloud Load Balancing resources.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “If a log entry matches the filter of the alerting policy, then Cloud Logging extracts labels and forwards the data to Cloud Monitoring.”
• Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
• Cloud Logging works with Cloud VPN From the official documentation: “Cloud VPN logs are stored in [Cloud Logging](/logging/docs).”
• Cloud Logging works with Google SecOps From the official documentation: “This document explains how to integrate Cloud Logging with Google Security Operations.”
• Cloud Monitoring works with Cloud NAT From the official documentation: “Metrics for Cloud NAT are batched and exported to Monitoring every one minute.”
• Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• Cloud Monitoring works with Compute Engine From the official documentation: “Many Google services like Compute Engine send telemetry to Cloud Monitoring.”
• Cloud Monitoring works with Google SecOps From the official documentation: “Google SecOps uses Cloud Monitoring to send the ingestion notifications.”
• Cloud NAT works with Compute Engine From the official documentation: “A Cloud NAT gateway provides outgoing connectivity for Compute Engine virtual machine (VM) instances without external IP addresses.”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• Cloud Service Mesh depends on Cloud Monitoring From the official documentation: “Cloud Service Mesh uses Cloud Monitoring to provide automatic telemetry and logs.”
• Cloud Service Mesh works with Private Service Connect From the official documentation: “Published service backends let you configure regional Cloud Service Mesh to route traffic to published services through Private Service Connect.”
• Private Service Connect is an alternative to VPC Network Peering From the official documentation: “Use VPC Network Peering if you need to insert NVAs or if your application doesn't support Private Service Connect”
• 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.”
• VPC Service Controls secures Compute Engine From the official documentation: “To further protect your Compute Engine resources, you can protect them using [VPC Service Controls](/vpc-service-controls/docs/overview).”
• Apigee works with Cloud Load Balancing From the official documentation: “Load balancer configured to send API calls to Apigee”
• Apigee works with Cloud Logging From the official documentation: “This page describes how to find and use [Cloud Logging](/logging/docs) to query and view maintenance logs for an Apigee instance.”