internal-load-balancer

问题 What is the difference between the internal and external load balancer? Assume I created an internal load balancer inside a VPC. Is it possible to access the internal load balancer outside the VPC? Consider I have two AWS accounts A and B. I created an internal load balancer in account A. Is it possible to attach the internal load balancer to Route 53 in account B? 回答1: An internal load balancer is assigned to a private subnet and does not have a public IP. It cannot be accessed by a client

来源： https://stackoverflow.com/questions/58818376/how-to-make-gke-clusters-communicate-using-private-ips-or-networks

来源： https://stackoverflow.com/questions/32019399/nginx-proxy-pass-to-variable-with-trailing-slash-fails

问题 We are in the process of setting up a service on GCP that will serve requests from both the internet and from other services inside of our VPC. We already have a global load-balancer setup and want all traffic to our new service to be load-balanced as well. Is it advisable to have our internal services use the global LB address when trying to reach the new service? Or should we be setting up internal LBs behind the global LB for internal services to use? If we were to use the global LB for

问题 We are in the process of setting up a service on GCP that will serve requests from both the internet and from other services inside of our VPC. We already have a global load-balancer setup and want all traffic to our new service to be load-balanced as well. Is it advisable to have our internal services use the global LB address when trying to reach the new service? Or should we be setting up internal LBs behind the global LB for internal services to use? If we were to use the global LB for

问题 We are in the process of setting up a service on GCP that will serve requests from both the internet and from other services inside of our VPC. We already have a global load-balancer setup and want all traffic to our new service to be load-balanced as well. Is it advisable to have our internal services use the global LB address when trying to reach the new service? Or should we be setting up internal LBs behind the global LB for internal services to use? If we were to use the global LB for

问题 I googled for load balancing but the only thing I can find is the working theory, which at the moment, is the "easy" part for me. But zero examples of how to implement one. I have several questions pertaining load balancing: I have a domain (example.com) and I behind it I have a load balancing server (lets call it A ) which, according to the theory, will ask the client to close the connection with A, and connect to B, a sub-server and carry on the request with B. Will the client, in a web

问题 I have microservices(in different programming languages) running on an EC2 instance. On production I notice a few 502 Bad Gateway Errors when these services try to interact with each other. Also in the logs of the requested service it doesn't show any api call is being hit example service A calls service B, but in service B logs there is nothing to indicate that a call came from service A. Can it be AWS load balancer issue? Any help would be appreciated. Thanks in advance. Solution tried: We

问题 Hoping someone can help here, is there any specific option i need to be aware off that will make the azure standard load balancer picks up (show) a availability set in the backend pool configuration? Basically, I have created a AS and it has one vm (for now), and then I created the azure "internal" load balancer with Standard SKU but when i try to create a bep it only provides an option of virtual network in the drop down list with respect to the associations. I tried to create the load

问题 I got two Vnets: Vnet #1: 1 VM with Public (internet facing) IP load balancer - internet connected App VMs. Vnet #2: 3 VMs with public (internet facing) IP load balancer - internet and private DB servers (the load balancer is using public ip so that I could access the DBs). I set up a peering between Vnet1 & Vnet2 so that the communication between them will be private/internal and fast with no internet routing. I want to access the DBs (using a load balancer) in Vnet2 from Vnet1 - so in the