privately used public IP addresses

Related topics

• GKE works with privately used public IP addresses From the official documentation: “This page shows how to apply privately used public IP (PUPI) addresses to Google Kubernetes Engine (GKE) Pod address blocks.”
• IP address masquerading works with privately used public IP addresses From the official documentation: “If the consumer's VPC already uses the same PUPI range as the producer, direct communication from producer Pods isn't possible. Instead, the producer can enable IP address masquerading, where the Pod IP addresses are hidden behind the producer's node IP addresses.”
• privately used public IP addresses depends on IP Masquerade agent From the official documentation: “When you use PUPIs, you must [configure the IP masquerade agent](/kubernetes-engine/docs/how-to/ip-masquerade-agent).”
• privately used public IP addresses works with Virtual Private Cloud From the official documentation: “Privately Used Public IP (PUPIs) addresses are addresses that you can use privately within your Google Cloud Virtual Private Cloud (VPC) network.”
• 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 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.”
• 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.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• 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 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:”
• 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”
• 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.”
• VPC firewall rules is part of Virtual Private Cloud From the official documentation: “As with any cloud-based project, you should tune your VPC's firewall rules to restrict network access only to the IP ranges or subnetworks that your applications connect from.”
• Cloud Run works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
• Cloud Run is an alternative to Compute Engine From the official documentation: “The decision of whether to use Cloud Run, GKE, or Compute Engine as your application host involves trade-offs between configuration flexibility and management effort.”
• Cloud Run works with Virtual Private Cloud From the official documentation: “Send outbound traffic from Cloud Run to a VPC network.”
• Compute Engine works with GKE From the official documentation: “For example, Google Kubernetes Engine (GKE) can cause usage in Compute Engine.”
• Compute Engine works with Virtual Private Cloud From the official documentation: “Google Cloud Virtual Private Cloud (VPC) provides networking functionality to Compute Engine virtual machine (VM) instances, Google Kubernetes Engine (GKE) containers, and serverless workloads.”
• Compute Engine works with VPC Network Peering From the official documentation: “VPC Network Peering works with [Compute Engine](/compute/docs), [GKE](/kubernetes-engine/docs), and [App Engine flexible environment](/appengine/docs/flexible).”
• 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 Virtual Private Cloud From the official documentation: “Google Kubernetes Engine (GKE) networking uses and extends the software-defined networking (SDN) infrastructure provided by Virtual Private Cloud (VPC).”
• GKE works with Virtual Private Cloud From the official documentation: “The following example creates a GKE cluster and a Virtual Private Cloud (VPC) network that supports GKE.”
• GKE depends on VPC firewall rules From the official documentation: “GKE uses Virtual Private Cloud (VPC) firewall rules to control incoming and outgoing traffic to your Pods and nodes.”
• GKE configures VPC firewall rules From the official documentation: “Google Kubernetes Engine creates and manages firewall rules automatically when you create a cluster or resources in the cluster (including Services and Ingresses).”
• GKE works with VPC Network Peering From the official documentation: “VPC Network Peering works with [Compute Engine](/compute/docs), [GKE](/kubernetes-engine/docs), and [App Engine flexible environment](/appengine/docs/flexible).”
• IP Masquerade agent is part of GKE From the official documentation: “If you have not configured an IP masquerade agent for the cluster, GKE automatically ensures that Pod to Pod communication is not masqueraded.”
• 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 part of Virtual Private Cloud From the official documentation: “VPC includes VPC Network Peering, Private Service Connect, private services access, and Shared VPC.”
• Private Service Connect works with Virtual Private Cloud From the official documentation: “[Private Service Connect](https://cloud.google.com/private-service-connect) | Create a private and secure connection from your VPCs to Google, third parties, or your own services.”
• VPC firewall rules secures Private Service Connect From the official documentation: “You can use VPC firewall rules and firewall policies to control network-level access to Private Service Connect resources.”
• VPC Network Peering is part of Virtual Private Cloud From the official documentation: “VPC includes VPC Network Peering, Private Service Connect, private services access, and Shared VPC.”