advanced traffic management

Related topics

• advanced traffic management configures backend service From the official documentation: “With advanced traffic management, you can configure how a destination backend service is selected and how traffic is distributed among the backends for that destination service.”
• advanced traffic management is part of Cloud Service Mesh From the official documentation: “Cloud Service Mesh supports capabilities such as advanced traffic management that are configurable using policies.”
• 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.”
• Cloud Logging works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh integrates with Cloud Logging and Cloud Monitoring.”
• 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.”
• 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 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 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.”
• 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 Logging From the official documentation: “After you enable logging on the backend service, HTTP or HTTPS requests are logged by using [Cloud Logging](/logging/docs) logs requests.”
• 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.”
• 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 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 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.”
• 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.”