Gateway API

Related topics

• Cloud Service Mesh works with Gateway API From the official documentation: “Update the mesh to use the Gateway API:”
• Gateway API configures Cloud Service Mesh From the official documentation: “You can configure a Cloud Service Mesh using Gateway API.”
• 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 API works with GKE Gateway controller From the official documentation: “GKE uses the GKE Gateway controller to interact with the Gateway API.”
• Gateway API is an alternative to Ingress From the official documentation: “For public HTTP(S) applications, use Ingress or Gateway API.”
• GatewayClass is part of Gateway API From the official documentation: “This step installs the Gateway API custom resource definitions including the `GatewayClass`, `Gateway`, and `HTTPRoute` resources.”
• GKE Gateway controller depends on Gateway API From the official documentation: “Once installed, you can use the GKE Gateway controller.”
• 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.”
• 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.”
• external Application Load Balancer works with Identity-Aware Proxy From the official documentation: “Enable IAP on the external Application Load Balancer”
• 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 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”
• 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 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.”
• 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 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 Gateway From the official documentation: “This document describes how to use Cloud Load Balancing as a gateway to get traffic into your mesh”
• 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 Service Mesh works with Gateway From the official documentation: “Update the mesh to use the Gateway API:”
• Cloud Service Mesh works with GKE Gateway controller From the official documentation: “For service ingress traffic into the service mesh, the blueprint uses the GKE Gateway controller.”
• Cloud Service Mesh depends on Google Kubernetes Engine From the official documentation: “Cloud Service Mesh service security is supported only with GKE.”
• Cloud Service Mesh 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`:”
• 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.”
• GatewayClass configures Gateway From the official documentation: “Network Service Tiers on Gateway are controlled by the GatewayClass resource.”
• GatewayClass works with GKE From the official documentation: “This page lists the capabilities of the [GatewayClass](/kubernetes-engine/docs/concepts/gateway-api#gateway_resources) resources available on Google Kubernetes Engine (GKE) and their supported specifications.”
• GKE configures Google Cloud Armor From the official documentation: “You can configure Cloud Armor by using Google Kubernetes Engine (GKE) ingress security policies.”
• GKE Gateway controller configures Cloud Load Balancing From the official documentation: “The controller reconciles Cloud Load Balancing resources to implement the networking behavior that's specified by the Gateway resources.”
• GKE Gateway controller is an alternative to Ingress From the official documentation: “The GKE Gateway controller is Google's implementation of the Gateway API and is designed to be a more expressive, flexible, and extensible successor to the Ingress resource.”
• Google Cloud Armor secures Cloud Service Mesh From the official documentation: “[Cloud Armor](https://cloud.google.com/armor) can defend against external distributed denial-of-service (DDoS) and Layer 7 attacks. It serves as a Web Application Firewall (WAF) to protect the mesh from network attacks.”
• Google Cloud Armor works with Google Kubernetes Engine From the official documentation: “The following sections describe how Cloud Armor works with GKE.”
• Google Cloud Armor secures Ingress From the official documentation: “For application load balancers (Ingress), you can use more advanced security services when exposing HTTP(S) applications: - Google Cloud Armor: this service is a web-application firewall (WAF) that helps protect your applications from DDoS attacks and other web-based threats.”
• Identity-Aware Proxy secures Cloud Load Balancing From the official documentation: “IAP secures authentication and authorization of all requests to Cloud Run, App Engine, Cloud Load Balancing (HTTPS), and internal HTTP load balancing.”
• Identity-Aware Proxy secures Cloud Service Mesh From the official documentation: “The IAP integration with Cloud Service Mesh enables you to safely access services based on Google's [BeyondCorp principles](/beyondcorp).”
• 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.”
• Identity-Aware Proxy secures Google Kubernetes Engine From the official documentation: “Identity-Aware Proxy (IAP) is a cloud-native alternative to traditional VPNs that manages access to applications running in Cloud Run, App Engine, Compute Engine, and GKE.”
• Identity-Aware Proxy works with Ingress From the official documentation: “IAP is integrated through [Ingress](/kubernetes-engine/docs/concepts/ingress) for GKE.”
• Identity-Aware Proxy secures Ingress From the official documentation: “For application load balancers (Ingress), you can use more advanced security services when exposing HTTP(S) applications: - Google Cloud Armor: this service is a web-application firewall (WAF) that helps protect your applications from DDoS attacks and other web-based threats. -…”
• Ingress configures Cloud Load Balancing From the official documentation: “Always modify the properties of the Load Balancer using the Ingress object.”
• Ingress configures external Application Load Balancer From the official documentation: “[Set up an external Application Load Balancer with Ingress](#load-balancing).”