关于“Deployment Manager: Adding load balancing”的评价

Thomas W. · 已于 over 7 years前审核

Shamsheer Ali S. · 已于 over 7 years前审核

Flavio B. · 已于 over 7 years前审核

Christopher S. · 已于 over 7 years前审核

Fengping H. · 已于 over 7 years前审核

Maksim U. · 已于 over 7 years前审核

Luisa O. · 已于 over 7 years前审核

Parmendra P. · 已于 over 7 years前审核

Thiago L. · 已于 over 7 years前审核

Iain W. · 已于 over 7 years前审核

Mohammed Z. · 已于 over 7 years前审核

ok

RICARDO L. · 已于 over 7 years前审核

Kostiantyn P. · 已于 over 7 years前审核

Koji Y. · 已于 over 7 years前审核

Anupam N. · 已于 over 7 years前审核

Good

Víctor E. · 已于 over 7 years前审核

Jhon I. · 已于 over 7 years前审核

Angeline G. · 已于 over 7 years前审核

Christiaan H. · 已于 over 7 years前审核

Oscar M. · 已于 over 7 years前审核

Davide P. · 已于 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. · 已于 over 7 years前审核

Prathamesh s. · 已于 over 7 years前审核

Robin A. · 已于 over 7 years前审核