<p>When you create a <code>Service</code> of type <code>LoadBalancer</code> in Kubernetes, does it create a brand new external load balancer, or does it just create a single load balancer for the first <code>Service</code> of type <code>LoadBalancer</code> and re-use that same load balancer for all subsequent <code>Service</code>s of type <code>LoadBalancer</code>?</p>
<p>This question is of particular importance, because spinning up a separate load balancer for every service would be cost prohibitive for me.</p>
<p>If it is specific to the cloud provider, I am using Azure, but I would be curious to know if other cloud providers differ.</p>

Jonathan Wilbur
<p>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 <code>kubernetes</code> load balancer present inside the cluster managed resource-group (the MC_* one)</p>
<p>In AWS and GCP a new load balancer is created for every instance of a service.</p>
