Internal Load Balancer

Related topics

• Internal Load Balancer depends on health check From the official documentation: “The load balancer uses a health check which ensures that traffic is directed to the active node of the WSFC.”
• forwarding rule is part of Internal Load Balancer From the official documentation: “Create a forwarding rule for the load balancer:”
• health check works with Internal Load Balancer From the official documentation: “In a Pacemaker configuration on Google Cloud Platform, the health check primitive and the Internal Load Balancer (ILB) primitive work together for high availability.”
• backend service works with health check From the official documentation: “Add the health check to the backend service.”
• backend service depends on health check From the official documentation: “Each backend service must reference a single health check.”
• backend service is part of internal passthrough Network Load Balancer From the official documentation: “An internal passthrough Network Load Balancer's backend service is regional.”
• health check is part of internal passthrough Network Load Balancer From the official documentation: “The following internal passthrough Network Load Balancer components: - A health check for the backend service.”
• forwarding rule depends on backend service From the official documentation: “Create a forwarding rule for the backend service.”
• forwarding rule is part of internal passthrough Network Load Balancer From the official documentation: “An internal passthrough Network Load Balancer has a frontend (the forwarding rule) and a backend (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 works with forwarding rule From the official documentation: “Connect the forwarding rule to the backend service.”
• 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.”
• forwarding rule works with internal passthrough Network Load Balancer From the official documentation: “You have a forwarding rule to direct network traffic to an internal passthrough Network Load Balancer whose backends provide packet mirroring.”
• health check is part of Cloud Service Mesh From the official documentation: “During Cloud Service Mesh setup, you configure several load-balancing components: - The backend service, which contains configuration values. - A health check, which provides health checking for the VMs and Google Kubernetes Engine (GKE) Pods in your deployment.”
• internal passthrough Network Load Balancer depends on backend service From the official documentation: “A backend service is necessary for creating an internal passthrough Network Load Balancer.”
• backend service is an alternative to forwarding rule From the official documentation: “You can enable IAP on a Compute Engine [backend service](/load-balancing/docs/backend-service) or on a Compute Engine [forwarding rule](/load-balancing/docs/forwarding-rule-concepts).”
• backend service is part of global external Application Load Balancer From the official documentation: “Global external Application Load Balancers use the `EXTERNAL_MANAGED` load balancing scheme and global load balancing components, such as the forwarding rule, URL map, and backend service.”
• Cloud Service Mesh depends on forwarding rule From the official documentation: “Cloud Service Mesh then looks for forwarding rules that have the `INTERNAL_SELF_MANAGED` load-balancing scheme and reference the same VPC network name.”
• Cloud Service Mesh works with forwarding rule From the official documentation: “Cloud Service Mesh then looks for forwarding rules that have the `INTERNAL_SELF_MANAGED` load-balancing scheme and reference the same VPC network name.”
• forwarding rule is part of global external Application Load Balancer From the official documentation: “Get the external IP address from the frontend forwarding rule of the load balancer by entering the following command in your terminal:”
• global external Application Load Balancer depends on health check From the official documentation: “When these instances report an unhealthy status, they fail the load balancing health check, prompting the load balancer to stop directing traffic to these instances.”
• global external Application Load Balancer works with health check From the official documentation: “- [Health check](/load-balancing/docs/health-check-concepts): a policy used by the load balancer to evaluate the responsiveness of the application on each VM instance.”
• health check is part of backend service From the official documentation: “Create a backend service that includes an instance group and health check.”
• health check configures backend service From the official documentation: “gcloud compute backend-services create grpc-gke-helloworld-service \ --global \ --load-balancing-scheme=INTERNAL_SELF_MANAGED \ --protocol=GRPC \ --health-checks grpc-gke-helloworld-hc”
• internal passthrough Network Load Balancer depends on health check From the official documentation: “To support high-availability failover of SAP NetWeaver, you must configure an internal passthrough Network Load Balancer with two separate backend services and health checks: one for the ASCS and one for the ERS.”