Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML Services
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Network Load Balancer
  • Getting started
    • Overview
    • Network load balancer types
    • Listener
    • Targets and target groups
    • Health checks
    • Implementation specifics
    • Use cases
    • Best practices
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • VMs
  • Use cases
  • Instance group
  • Use cases
  • Managed Service for Kubernetes cluster
  • Use cases
  1. Concepts
  2. Use cases

Network load balancer use cases

Written by
Yandex Cloud
Updated at June 10, 2025
  • VMs
    • Use cases
  • Instance group
    • Use cases
  • Managed Service for Kubernetes cluster
    • Use cases

VMsVMs

A load balancer’s incoming traffic is distributed in a certain way among VMs located in the target groups downstream of the load balancer.

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.

Use casesUse cases

  • Architecture and protection of a basic web service
  • Deploying Microsoft Exchange
  • Migrating services from an NLB to L7 ALB for DDoS protection using Yandex Smart Web Security

Instance groupInstance 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.

Use casesUse cases

  • Configuring a fault-tolerant architecture in Yandex Cloud
  • Updating an instance group under load
  • Deploying Microsoft Exchange
  • Deploying an Always On availability group with an internal network load balancer
  • Migrating services from an NLB to L7 ALB for DDoS protection using Yandex Smart Web Security

Managed Service for Kubernetes clusterManaged 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. Then the cluster itself will create network load balancer objects according to the provided manifests and will monitor the load balancer's target group receiving VMs from all node groups of that 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.

Use casesUse cases

  • Migrating services from an NLB with a Yandex Managed Service for Kubernetes cluster as a target to an L7 ALB

Was the article helpful?

Previous
Implementation specifics
Next
Best practices
© 2025 Direct Cursus Technology L.L.C.