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”
• 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 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.”
• HTTPRoute is an alternative to Ingress From the official documentation: “In this phase, you translate your Ingress manifest into an HTTPRoute resource.”
• 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.”
• backend service works with network endpoint groups From the official documentation: “Add the previously created NEG as a backend to the backend service.”
• 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.”
• Gateway API configures Cloud Service Mesh From the official documentation: “You can configure a Cloud Service Mesh using Gateway API.”
• 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”
• 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 Load Balancing works with Google Cloud Armor From the official documentation: “For applications that are exposed behind Cloud Load Balancing, use Google Cloud Armor default policies or configure your own policies to add Layer 3 to Layer 7 network protection for externally-facing applications or services.”
• Cloud Service Mesh works with Gateway API From the official documentation: “Update the mesh to use the Gateway API:”
• Cloud Service Mesh works with network endpoint groups From the official documentation: “Later, this deployment guide discusses how you can configure these NEGs as backends for Cloud Service Mesh services.”
• 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 managed instance group From the official documentation: “It configures the load balancer to connect to the instance group.”
• 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.”
• 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.”
• Gateway API works with GKE Gateway controller From the official documentation: “GKE uses the GKE Gateway controller to interact with the Gateway API.”
• network endpoint groups is part of backend service From the official documentation: “Add the previously created NEG as a backend to the backend service.”
• 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 Google Cloud Armor From the official documentation: “If you use one of the following load balancers, you can add additional protection to your applications by enabling Cloud Armor on the backend service during load balancer creation:”
• 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.”
• 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 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 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 network endpoint groups From the official documentation: “- **[Network endpoint groups (NEGs)](/load-balancing/docs/negs)**: how GKE Services use NEGs to integrate with Cloud Load Balancing.”
• 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 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 configures network endpoint groups From the official documentation: “When using the `TRAFFIC_DIRECTOR` control plane implementation, Cloud Service Mesh creates network endpoint groups by adding `cloud.google.com/neg` annotations to services for load balancing.”
• Gateway API configures backend service From the official documentation: “Service Labels: Information about the backend service (xDS cluster) that the RPC is being routed to. Note that this is only available if the backend service has been configured through the Gateway API.”
• Gateway API is an alternative to Ingress From the official documentation: “For public HTTP(S) applications, use Ingress or Gateway API.”
• 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 depends on Gateway API From the official documentation: “Once installed, you can use the GKE Gateway controller.”
• 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 is part of Cloud Load Balancing From the official documentation: “Consequently, RoCE VPC networks for bare metal instances don't support load balancer features,<br>including [Google Cloud Armor](/armor/docs/cloud-armor-overview).”
• 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 Identity-Aware Proxy From the official documentation: “This document explains how Cloud Armor interacts with VPC firewall rules, Identity-Aware Proxy (IAP), Google Kubernetes Engine (GKE), Cloud CDN, and Global Front End.”
• 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 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 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.”
• 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).”
• managed instance groups is an alternative to network endpoint groups From the official documentation: “These backends are either VMs in managed instance groups (MIGs) or containers in NEGs.”