HTTPRoute

Related topics

• backend service works with HTTPRoute From the official documentation: “You can now connect them using an HTTPRoute resource that associates a hostname with a Backend Service.”
• Cloud Service Mesh works with HTTPRoute From the official documentation: “Configuring Envoy sidecar proxy configuration with HTTP services with regional HTTPRoute and regional Cloud Service Mesh”
• Envoy proxy works with HTTPRoute From the official documentation: “Envoy sidecar deployments support all Routes (`HTTPRoute`, `GRPCRoute`, `TCPRoute`, and `TLSRoute`).”
• HTTPRoute configures backend service From the official documentation: “You can now connect them using an HTTPRoute resource that associates a hostname with a Backend Service.”
• HTTPRoute configures Cloud Load Balancing From the official documentation: “When you deploy the `HTTPRoute` resource it creates an external Layer 7 Cloud Load Balancing resource and exposes the frontend `ServiceImport` backed by the frontend services that run in the *std-west*, *auto-east*, and *auto-central* clusters.”
• HTTPRoute depends on Envoy proxy From the official documentation: “`HTTPRoute`, which is available only in meshes using Envoy proxies.”
• HTTPRoute configures Envoy proxy From the official documentation: “When you use the `HTTPRoute` resource to configure the Envoy proxies to send HTTP requests, all the capabilities in this document are available.”
• HTTPRoute configures Traffic splitting From the official documentation: “HTTPRoute resources let you configure weights on a list of Services. The relative weights between Services define the split of traffic between them. This is useful for splitting traffic during rollouts, canarying changes, or for emergencies.”
• backend service works with managed instance group From the official documentation: “Add the backend instance group to the backend service.”
• managed instance group is part of backend service From the official documentation: “Add the managed instance group to the backend service.”
• Traffic Director is part of Cloud Service Mesh From the official documentation: “`TRAFFIC_DIRECTOR`: The core infrastructure of Google Cloud serves as the Cloud Service Mesh control plane.”
• Cloud Service Mesh configures Envoy proxy From the official documentation: “Cloud Service Mesh configures the Envoy proxy to do the following:”
• 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 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.”
• Identity-Aware Proxy secures Cloud Run From the official documentation: “IAP provides a central authorization layer for HTTPS applications deployed to Cloud Run.”
• backend service works with managed instance groups From the official documentation: “Add the managed instance group to the backend service.”
• 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 Traffic Director From the official documentation: “**Note:** This is only applicable to Cloud Service Mesh with Traffic Director implementation.”
• Envoy proxy is part of Cloud Service Mesh From the official documentation: “Cloud Service Mesh works by placing an [Envoy](https://www.envoyproxy.io) sidecar proxy in each Pod.”
• Envoy proxy depends on Cloud Service Mesh From the official documentation: “Envoy proxies running as sidecars receive their service routing configuration from Cloud Service Mesh.”
• backend service is part of Cloud Service Mesh From the official documentation: “you create a new backend service in Cloud Service Mesh.”
• backend service configures Cloud Service Mesh From the official documentation: “Backend services are configuration resources that provide information to Cloud Service Mesh, including the backends, such as managed instance groups, to which the backend service routes traffic.”
• Cloud Service Mesh works with Envoy proxy From the official documentation: “Create a VM with an Envoy proxy that is connected to Cloud Service Mesh.”
• managed instance groups is part of backend service From the official documentation: “Add the managed instance group to the backend service.”
• backend service depends on managed instance group From the official documentation: “As a part of this step, you need to assign the health check that you created to the backend service and add the instance group as the backend to the backend service.”
• 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 works with managed instance group From the official documentation: “It configures the load balancer to connect to the instance group.”
• Cloud Run works with Traffic Director From the official documentation: “This page provides a reference for the APIs that are used to configure Cloud Service Mesh for Cloud Run workloads.”
• Cloud Service Mesh works with managed instance group From the official documentation: “Cloud Service Mesh is now configured to load balance traffic for the services specified in the HTTPRoute across backends in the managed instance group.”
• Cloud Service Mesh works with managed instance groups From the official documentation: “Cloud Service Mesh monitors these MIGs and NEGs so that it knows when instances and endpoints are created and removed.”
• backend service is part of Cloud Load Balancing From the official documentation: “Quotas and limits for Cloud Load Balancing resources such as forwarding rules, backend services, and more.”
• backend service configures Cloud Load Balancing From the official documentation: “A [backend service](/compute/docs/reference/rest/v1/backendServices) defines how Cloud Load Balancing distributes traffic.”
• backend service works with Cloud Service Mesh From the official documentation: “A deployment can have multiple Cloud Service Mesh backend services that run behind one external Application Load Balancer.”
• backend service works with Identity-Aware Proxy From the official documentation: “Certain Google Cloud load balancers routing to an Identity-Aware Proxy (IAP) enabled [Backend Service](https://cloud.google.com/load-balancing/docs/https) could have been vulnerable to an untrusted party under limited conditions.”
• backend service is part of load balancer From the official documentation: “gdcloud compute backend-services create - Create backend services for a load balancer.”
• 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 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 configures load balancer From the official documentation: “You use [Cloud Load Balancing](/load-balancing/docs/load-balancing-overview) to create a load balancer that uses the `asm-ingressgateway` Services in both clusters as backends.”
• Cloud Load Balancing works with managed instance groups From the official documentation: “Use [managed instance groups (MIGs)](/compute/docs/instance-groups#managed_instance_groups) to create groups of VMs so that load balancers can direct traffic to more than one VM in case a single VM becomes unhealthy.”
• Cloud Load Balancing works with Traffic Director From the official documentation: “This section configures Cloud Service Mesh using Compute Engine load balancing resources.”
• Cloud Run works with Identity-Aware Proxy From the official documentation: “Enable IAP on the Cloud Run service.”
• Cloud Run works with load balancer From the official documentation: “It configures the load balancer to connect to the Cloud Run service.”
• Cloud Service Mesh works with load balancer From the official documentation: “Deploy a simple application on Cloud Service Mesh with a load balancer, and integrate with IAP.”
• Cloud Service Mesh depends on Traffic Director From the official documentation: “This feature is only available to managed Cloud Service Mesh users using Traffic Director as control plane and requires data plane version 1.19.10-asm.22 or later.”
• Identity-Aware Proxy secures backend service From the official documentation: “This lets you enforce IAP-based access control for your backend services.”
• 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 works with load balancer From the official documentation: “Identity-Aware Proxy is enabled on a load balancer, and will support *at most* the location capabilities of the chosen load balancer.”
• Identity-Aware Proxy works with Traffic Director From the official documentation: “You authenticate users who are accessing any service exposed on a Cloud Service Mesh ingress gateway by using [Identity-Aware Proxy (IAP)](/iap).”
• load balancer works with managed instance group From the official documentation: “Abandoning an instance from a group also removes the instance from [load balancers](/compute/docs/load-balancing) that were assigned to the managed instance group.”
• managed instance group is part of managed instance groups From the official documentation: “You can build highly available deployments of stateful workloads on VMs using stateful managed instance groups (stateful MIGs).”
• Traffic splitting is part of Cloud Run From the official documentation: “Cloud Run lets you specify which revisions should receive traffic and to specify traffic percentages that are received by a revision. This feature lets you rollback to a previous revision, gradually deploy a revision, and split traffic between multiple revisions.”
• Traffic splitting is part of Traffic Director From the official documentation: “This document provides instructions for configuring Cloud Service Mesh with the following traffic management features: - Route matching - Traffic splitting”