session affinity

Related topics

• session affinity is part of backend service From the official documentation: “By default, the backend service of the load balancer is created with a session affinity value set to `NONE`.”
• backend service configures session affinity From the official documentation: “Use the following commands to update the `l7-xlb-backend-service` backend service to different types of session affinity:”
• generated cookie affinity is part of session affinity From the official documentation: “These procedures show you how to update a backend service for the example regional external Application Load Balancer so that the backend service uses generated cookie affinity, header field affinity, or HTTP cookie affinity.”
• session affinity is part of App Engine From the official documentation: “To allow App Engine to send requests by the same user to the same instance, you can enable session affinity.”
• session affinity is part of Cloud Load Balancing From the official documentation: “You can take advantage of [session affinity](/compute/docs/load-balancing/http#session_affinity) in Cloud Load Balancing. This feature ensures that all requests from a single client are routed to the same app instance.”
• session affinity is part of Cloud Run From the official documentation: “Even if you use Cloud Run [session affinity](/run/docs/configuring/session-affinity), it is possible for new requests to be load balanced to active containers, which allows containers to scale in.”
• session affinity works with Traffic splitting From the official documentation: “If you are splitting traffic between multiple revisions with session affinity enabled, see [Session affinity and traffic splitting](/run/docs/configuring/session-affinity#affinity-and-traffic-splitting) for details on the effect of session affinity on traffic splitting.”
• 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.”
• App Engine is an alternative to Cloud Run From the official documentation: “App Engine and Cloud Run are Google Cloud platforms for hosting apps and services.”
• 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 App Engine From the official documentation: “Securing App Engine apps Enable IAP for App Engine apps.”
• Identity-Aware Proxy secures Cloud Run From the official documentation: “IAP provides a central authorization layer for HTTPS applications deployed to Cloud Run.”
• API Gateway works with Cloud Run From the official documentation: “API Gateway only supports Cloud Run gRPC services at this time.”
• 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 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 CDN works with Cloud Load Balancing From the official documentation: “Because Cloud CDN integrates with Cloud Load Balancing, Cloud CDN's approach differs from the approach of conventional CDNs.”
• Cloud CDN works with Google Cloud Armor From the official documentation: “You can use Cloud Armor with Cloud CDN to protect the CDN origin servers.”
• API Gateway works with Cloud CDN From the official documentation: “Cloud CDN is supported for backend services with Cloud Run, Cloud Run functions, API Gateway, and App Engine backends.”
• App Engine works with Identity-Aware Proxy From the official documentation: “Validate a JWT passed to your App Engine app by Identity-Aware Proxy.”
• backend service works with Cloud CDN From the official documentation: “Clear the checkboxes of any backend services that you want to stop from using Cloud CDN.”
• Cloud CDN works with Cloud Run From the official documentation: “You can use [Cloud CDN](/cdn/docs/overview) to forward requests to Cloud Run and cache OCSP responses.”
• 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.”
• API Gateway works with App Engine From the official documentation: “Learn how to use API Gateway to manage and secure traffic to an App Engine backend service.”
• API Gateway is an alternative to Cloud Load Balancing From the official documentation: “To securely expose frontend applications to users, you can use Cloud Load Balancing or API Gateway.”
• API Gateway secures Cloud Run From the official documentation: “This page shows you how to set up API Gateway to manage and secure a [Cloud Run](/run/docs) backend service with gRPC.”
• API Gateway works with Google Cloud Armor From the official documentation: “These fields can be used to set up [Identity-Aware Proxy](/iap/docs), [Cloud CDN](/cdn/docs), and [Cloud Armor](/armor/docs) respectively with your API Gateway service.”
• API Gateway works with Identity-Aware Proxy From the official documentation: “These fields can be used to set up [Identity-Aware Proxy](/iap/docs), [Cloud CDN](/cdn/docs), and [Cloud Armor](/armor/docs) respectively with your API Gateway service.”
• App Engine works with Application Load Balancer From the official documentation: “### Load balancing for Cloud Run, Cloud Run functions, and App Engine applications”
• App Engine works with Cloud CDN From the official documentation: “Cloud CDN is supported for backend services with Cloud Run, Cloud Run functions, API Gateway, and App Engine backends.”
• App Engine works with Cloud Load Balancing From the official documentation: “If you want to use an IP address that only maps to your domain then you should instead [set up a load balancer with App Engine](/load-balancing/docs/https/setting-up-https-serverless).”
• Application Load Balancer works with backend service From the official documentation: “While integrating a backend service with Application Load Balancer, it's important to measure the performance of a backend service on its own, in the absence of a load balancer.”
• Application Load Balancer is part of Cloud Load Balancing From the official documentation: “To see an overview of all the Cloud Load Balancing products available, see [Cloud Load Balancing overview](/load-balancing/docs/load-balancing-overview). To determine which Cloud Load Balancing product to use, you must first determine the traffic type that your load balancers…”
• Application Load Balancer works with Cloud Run From the official documentation: “This page shows you how to deploy a regional external Application Load Balancer with a Cloud Run backend.”
• Application Load Balancer works with Identity-Aware Proxy From the official documentation: “For proxy load balancers such as the internal and external Application Load Balancers, we recommend that you use Identity-Aware Proxy (IAP) as your authentication method instead.”
• 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 works with Cloud Run From the official documentation: “Ensures that Cloud Run services are configured to accept traffic only from Internal sources and Cloud Load Balancing.”
• 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 Run works with Google Cloud Armor From the official documentation: “See Google Cloud Armor documentation to learn how to [use Google Cloud Armor with Cloud Run](/armor/docs/integrating-cloud-armor#serverless).”
• Cloud Run works with Identity-Aware Proxy From the official documentation: “Enable IAP on the Cloud Run service.”
• Google Cloud Armor secures Cloud CDN From the official documentation: “Cloud Armor helps protect Cloud CDN origin servers from application layer (L7) attacks, such as SQL injection (SQLi) and cross-site scripting (XSS).”
• 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 Run From the official documentation: “Google Cloud Armor helps you protect your Cloud Run services from multiple types of threats, including distributed denial-of-service (DDoS) attacks and application attacks like cross-site scripting (XSS) and SQL injection (SQLi).”
• 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.”
• 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).”
• Traffic splitting is part of App Engine From the official documentation: “If the tasks are created by an App Engine app, you can take advantage of App Engine traffic splitting ([Standard](/appengine/docs/standard/java/splitting-traffic)/[Flex](/appengine/docs/flexible/java/splitting-traffic)) to smooth traffic increases.”
• 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.”