Deployment Manager: como adicionar o balanceamento de carga avaliações

Thomas W. · Revisado há over 7 years

Shamsheer Ali S. · Revisado há over 7 years

Flavio B. · Revisado há over 7 years

Christopher S. · Revisado há over 7 years

Fengping H. · Revisado há over 7 years

Maksim U. · Revisado há over 7 years

Luisa O. · Revisado há over 7 years

Parmendra P. · Revisado há over 7 years

Thiago L. · Revisado há over 7 years

Iain W. · Revisado há over 7 years

Mohammed Z. · Revisado há over 7 years

ok

RICARDO L. · Revisado há over 7 years

Kostiantyn P. · Revisado há over 7 years

Koji Y. · Revisado há over 7 years

Anupam N. · Revisado há over 7 years

Good

Víctor E. · Revisado há over 7 years

Jhon I. · Revisado há over 7 years

Angeline G. · Revisado há over 7 years

Christiaan H. · Revisado há over 7 years

Oscar M. · Revisado há over 7 years

Davide P. · Revisado há over 7 years

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. · Revisado há over 7 years

Prathamesh s. · Revisado há over 7 years

Robin A. · Revisado há over 7 years