Deployment Manager: Adding load balancing Reviews

Thomas W. · Reviewed over 7 years ago

Shamsheer Ali S. · Reviewed over 7 years ago

Flavio B. · Reviewed over 7 years ago

Christopher S. · Reviewed over 7 years ago

Fengping H. · Reviewed over 7 years ago

Maksim U. · Reviewed over 7 years ago

Luisa O. · Reviewed over 7 years ago

Parmendra P. · Reviewed over 7 years ago

Thiago L. · Reviewed over 7 years ago

Iain W. · Reviewed over 7 years ago

Mohammed Z. · Reviewed over 7 years ago

ok

RICARDO L. · Reviewed over 7 years ago

Kostiantyn P. · Reviewed over 7 years ago

Koji Y. · Reviewed over 7 years ago

Anupam N. · Reviewed over 7 years ago

Good

Víctor E. · Reviewed over 7 years ago

Jhon I. · Reviewed over 7 years ago

Angeline G. · Reviewed over 7 years ago

Christiaan H. · Reviewed over 7 years ago

Oscar M. · Reviewed over 7 years ago

Davide P. · Reviewed over 7 years ago

This part is not so clear: From the point of view of the servers, they are just fine. And the servers are ready to receive traffic if a firewall rule targeted at the tag http permits the health check from the load balancer to forward traffic to the instances. View the firewall rules On the Products & services menu, click VPC Networks > Firewall rules There is no firewall rule to allow health checks from the load balancer to the instances. When a health check is used with Network load balancing, the health check probes come from a different range of addresses than for HTTP(S) (see reference). When a health check is used with HTTP(S), SSL proxy, TCP proxy, or Internal load balancing, the health check probes come from addresses in the ranges 130.211.0.0/22 and 35.191.0.0/16. https://cloud.google.com/compute/docs/load-balancing/health-checks Since this is an HTTP(S) load balancer, you will need to enable TCP traffic from 130.211.0.0/22 and 35.191.0.0/16 to instances with the tag http.

Sabi T. · Reviewed over 7 years ago

Prathamesh s. · Reviewed over 7 years ago

Robin A. · Reviewed over 7 years ago