When you create a Service of type LoadBalancer in Kubernetes, does it create a brand new external load balancer, or does it just create a single load balancer for the first Service of type LoadBalancer and re-use that same load balancer for all subsequent Services of type LoadBalancer?
This question is of particular importance, because spinning up a separate load balancer for every service would be cost prohibitive for me.
If it is specific to the cloud provider, I am using Azure, but I would be curious to know if other cloud providers differ.
On Azure I have observed that Kubernetes does not create a load balancer per service entry. In fact it creates a Load Balancing Rule in the kubernetes load balancer present inside the cluster managed resource-group (the MC_* one)
In AWS and GCP a new load balancer is created for every instance of a service.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With