Gateway

Related topics

• Gateway is part of Cloud Service Mesh From the official documentation: “Cloud Service Mesh gives you the option to deploy and manage gateways as part of your service mesh.”
• Gateway is part of Gateway API From the official documentation: “Gateway API uses separate resources, Gateways and Route resources, to deploy load balancers and routing rules.”
• Gateway depends on GatewayClass From the official documentation: “A Gateway can represent many different kinds of load balancing and routing depending on the GatewayClass it is derived from.”
• Cloud Load Balancing works with Gateway From the official documentation: “This document describes how to use Cloud Load Balancing as a gateway to get traffic into your mesh”
• Cloud Service Mesh works with Gateway From the official documentation: “Update the mesh to use the Gateway API:”
• external Application Load Balancer works with Gateway From the official documentation: “Google Cloud offers a wide range of load balancers that can act as the gateway to your mesh. This section discusses selecting a gateway, comparing the following options along dimensions relevant to the gateway pattern: - [Internal Application Load…”
• Gateway is part of Google Kubernetes Engine From the official documentation: “Create a GKE cluster using GKE version 1.27 or later with [Workload Identity Federation for GKE](/kubernetes-engine/docs/how-to/workload-identity) and [GKE Gateway](/kubernetes-engine/docs/how-to/deploying-gateways) enabled.”
• Gateway is an alternative to Ingress From the official documentation: “Gateway and Ingress are both open source standards for routing traffic and can be used simultaneously without conflict.”
• Gateway works with internal passthrough Network Load Balancer From the official documentation: “Google Cloud offers a wide range of load balancers that can act as the gateway to your mesh. This section discusses selecting a gateway, comparing the following options along dimensions relevant to the gateway pattern: - [Internal Application Load…”
• Gateway works with Route From the official documentation: “In the service routing API model, `Route` resources are attached to `Mesh` or `Gateway` resources.”
• Gateway works with Service Extensions From the official documentation: “Additionally, Gateways can integrate with Service Extensions by using the GCPAuthzExtension resource.”
• GatewayClass configures Gateway From the official documentation: “Network Service Tiers on Gateway are controlled by the GatewayClass resource.”
• Identity-Aware Proxy secures Gateway From the official documentation: “Identity-Aware Proxy is the recommended way to secure your Gateway and is configured on the backend.”
• Route depends on Gateway From the official documentation: “The `Route` resource references one or more [`Mesh`](#mesh-resource) and [`Gateway`](#gateway-resource) resources to add the routes that are part of the corresponding `Mesh` or `Gateway` configuration.”
• external Application Load Balancer works with Google Cloud Armor From the official documentation: “Learn the value of adding Cloud CDN and Google Cloud Armor to an existing external Application Load Balancer deployment.”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Cloud Service Mesh works with Gateway API From the official documentation: “Update the mesh to use the Gateway API:”
• 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.”
• external Application Load Balancer works with Identity-Aware Proxy From the official documentation: “Enable IAP on the external Application Load Balancer”
• Identity-Aware Proxy secures Cloud Run From the official documentation: “There are two ways to enable Identity-Aware Proxy for your Cloud Run services.”
• 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 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.”
• external Application Load Balancer is an alternative to internal passthrough Network Load Balancer From the official documentation: “The ingress service can be paired with an external Application Load Balancer or an internal passthrough Network Load Balancer, but such configurations are not included in this demonstration setup.”
• Cloud Load Balancing works with Google Cloud Armor From the official documentation: “In addition to Cloud Armor quotas, products that use Cloud Armor have their own quotas. For example, see [Cloud Load Balancing quotas and limits](/load-balancing/docs/quotas).”
• 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 Service Mesh works with Google Kubernetes Engine From the official documentation: “A GKE Cluster with Cloud Service Mesh enabled”
• Cloud Service Mesh works with Identity-Aware Proxy From the official documentation: “Integrate Identity-Aware Proxy with Cloud Service Mesh”
• Gateway API configures Cloud Service Mesh From the official documentation: “You can configure a Cloud Service Mesh using Gateway API.”
• Cloud Run works with external Application Load Balancer From the official documentation: “When configured to listen for HTTP/2, Cloud Run automatically handles the HTTP/2 or gRPC traffic arriving from the Application Load Balancer.”
• Cloud Run works with Identity-Aware Proxy From the official documentation: “On the Cloud Run security page, find the checkbox for Identity-Aware Proxy (IAP).”
• 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 Load Balancing works with Service Extensions From the official documentation: “GKE uses Service Extensions to add custom logic into Cloud Load Balancing.”
• 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 Google Kubernetes Engine From the official documentation: “As an example, if you are using GKE, you can [use Cloud Logging to query](/logging/docs/view/building-queries) for GKE cluster audit logs.”
• Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• 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 Google Kubernetes Engine From the official documentation: “Improved security: take advantage of automatic IAM JWT injection for more secure communication between GKE and Cloud Run.”
• 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 Google Cloud Armor From the official documentation: “For Cloud Service Mesh rate limiting, Cloud Armor uses the security policy type `CLOUD_ARMOR_INTERNAL_SERVICE` and security policy rules use the `fairshare` action.”
• Gateway API works with GKE Gateway controller From the official documentation: “GKE uses the GKE Gateway controller to interact with the Gateway API.”
• GKE works with Identity-Aware Proxy From the official documentation: “GKE users can implement<br>IAP following this<br>[guidance](/iap/docs/enabling-kubernetes-howto)”
• GKE Gateway controller configures external Application Load Balancer From the official documentation: “In this section, you will configure an external Application Load Balancer (L7XLB) through the GKE Gateway controller to enable ingress traffic to the mesh.”
• Google Cloud Armor secures external Application Load Balancer From the official documentation: “The Google Cloud-managed load balancer applies an initial set of policies—for example, Cloud Armor protection if you are using an external Application Load Balancer.”
• Identity-Aware Proxy secures GKE From the official documentation: “Securing Google Kubernetes Engine apps Enable IAP for GKE apps.”
• Cloud Load Balancing works with Cloud Logging From the official documentation: “This page shows you how to configure and use [Cloud Logging](/logging) and [Cloud Monitoring](/monitoring) with Service Extensions callouts for Cloud Load Balancing.”
• Cloud Load Balancing works with Cloud Run From the official documentation: “If you are using Cloud Load Balancing with Cloud Run, configure custom error responses at the load balancer level.”
• Cloud Load Balancing is an alternative to Cloud Service Mesh From the official documentation: “If you want to use [Cloud Load Balancing, Ingress, or Cloud Service Mesh to handle the SSL configuration](/migrate/containers/docs/windows/prepare-windows-cluster#secure-access), then you need to set `protocol` to `http`:”
• Cloud Load Balancing works with GKE From the official documentation: “GKE and GKE Enterprise network controllers also support the deployment of Cloud Load Balancing for built-in integration with container networking.”
• Cloud Load Balancing works with GKE Gateway controller From the official documentation: “The GKE Gateway controller is Google's implementation of the Gateway API for Cloud Load Balancing.”
• Cloud Load Balancing works with Identity-Aware Proxy From the official documentation: “IAP also supports and seamlessly integrates with Cloud Load Balancing, making it the most efficient security management option for this tutorial.”
• Cloud Load Balancing is an alternative to Ingress From the official documentation: “If you want to use [Cloud Load Balancing, Ingress, or Cloud Service Mesh to handle the SSL configuration](/migrate/containers/docs/windows/prepare-windows-cluster#secure-access), then you need to set `protocol` to `http`:”
• Cloud Logging is an alternative to Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
• Cloud Logging works with Google Cloud Armor From the official documentation: “Each HTTP(S) request that is evaluated against a Cloud Armor security policy is logged through Cloud Logging.”
• Cloud Logging works with internal passthrough Network Load Balancer From the official documentation: “To gain operational insights into your internal passthrough Network Load Balancers, you can integrate [Cloud Logging](/logging) and [Cloud Monitoring](/monitoring).”
• Cloud Logging works with Service Extensions From the official documentation: “Service Extensions exports these log messages to Cloud Logging.”