Network load balancer use cases
VMs
Traffic coming to the load balancer is distributed in a certain way among the instances located in the target groups behind it.
If multiple traffic listeners are used on one load balancer, the traffic coming to these listeners will be distributed among all target groups connected to this load balancer simultaneously.
For example, traffic coming to "Listener-1" will be sent to instances in target groups 1 and 2.
For more granular traffic listening, instead of creating multiple listeners per load balancer, we recommend creating a separate load balancer for each service.
Instance group
When creating an instance group, a target group for the network load balancer will also be created, which will include all VMs from this group.
When adding or removing VMs from the group, the load balancer's target group will also reflect these changes.
Example of deploying an instance group with autoscaling and integration with a network load balancer.
Managed Service for Kubernetes cluster
To use a network load balancer as part of services within a Managed Service for Kubernetes cluster, you need to create a service of the LoadBalancer type. Next, the cluster will independently create network load balancer objects according to the manifests provided and monitor the composition of the load balancer's target group, which will include the VMs of all node groups of this cluster.
To learn more about deploying a service using a network load balancer in a Kubernetes cluster, see Granting access to an app running in a Kubernetes cluster.