Azure load balancer limitations, public vs private load balancer
Azure Load Balancer delivers high availability and network performance to your applications. It is a Layer 4 (TCP, UDP) load balancer that distributes incoming traffic among healthy instances of services defined in a load-balanced set.
Azure Load Balancer can be configured to:
- Load balance incoming Internet traffic to virtual machines. This configuration is known as Internet-facing load balancing.
- Load balance traffic between virtual machines in a virtual network, between virtual machines in cloud services, or between on-premises computers and virtual machines in a cross-premises virtual network. This configuration is known as internal load balancing.
- Forward external traffic to a specific virtual machine. – single VM LB
There are certain limitation using azure load balancer as below:
Internet-facing / public load balancer limitation ->
| public / internate facing load balance | internal / private load balance |
| we can add up to 100 load balancer per subscription | we can add up to 100 load balancer per subscription |
| backend pool vm / availability set can be added from any resource group across the subscription | backend pool vm / availability set needs to be in same resource group as LB or vnet |
| public LB comes with public ip address in frontend pool so we can access the LB over internet | private LB use internal ip from vnet and can be accessable in that vnet / peered vnet |
| only one availability set can associated to LB at a time | only one availability set can associated to LB at a time |
| the availability set associated with LB can also associate with one additional internal LB | the availability set associated with LB can also associate with one additional public LB |
| you can create multiple LB rules and backend pools based on availability set associated in backend pool, that means if you have 4 vm in AS (availability set) then you can create multiple backend pool and assign required vm to specific backend pool which then you can map to LB rules | you can create multiple LB rules and backend pools based on availability set associated in backend pool, that means if you have 4 vm in AS (availability set) then you can create multiple backend pool and assign required vm to specific backend pool which then you can map to LB rules |
| max 150 Load balancer rules can be created per load balancer | max 150 Load balancer rules can be created per load balancer |
| max 10 front end IP can be added per load balancer | max 10 front end IP can be added per load balancer
|
(Visited 2 times, 1 visits today)
Comments are closed.