关于AKS自动创建LoadBalancer的用途与用法的技术咨询

Hey there, let's clear up what that automatically created LoadBalancer in your AKS cluster is all about—this is a common point of confusion, so you’re not alone!

Core Purposes #

• Outbound Traffic Management：This LoadBalancer (usually named something like aks-<cluster-name>-lb in your auto-generated node resource group) is the default way AKS handles outbound public traffic for your cluster nodes and pods. If your cluster uses the Standard Load Balancer outbound type (the default for most AKS deployments), it manages NAT rules, provides stable public IPs for outbound traffic, and ensures traffic is distributed efficiently.
• Infrastructure Health & Control Plane Integration：It also handles critical cluster infrastructure traffic, like node health checks from Azure's control plane, and acts as a foundation if you later deploy LoadBalancer-type Services (it will reuse this existing LoadBalancer instead of creating a new one for each service, saving resources).

Practical Usage & Operations #

• Check Its Details：To get a full view of the LoadBalancer's configuration, use this Azure CLI command (replace placeholders with your cluster's info):

  az network lb show --resource-group MC_<your-resource-group>_<cluster-name>_<region> --name <aks-loadbalancer-name>
  

  Pro tip: The node resource group (starting with MC_) is auto-created when you spin up your AKS cluster—you can find it in the Azure Portal under your cluster's "Overview" tab.
• Set a Static Outbound IP：If you need a fixed public IP for your cluster's outbound traffic (instead of the default dynamic one), create a static public IP first, then update your existing cluster with:

  az aks update --resource-group <rg-name> --name <cluster-name> --load-balancer-outbound-ips <static-ip-resource-id>
  

• Never Delete It Randomly!：This LoadBalancer is a core part of your AKS infrastructure. Deleting it will break node connectivity to the public internet and Azure's control plane, leading to cluster instability. Only remove it if you're switching to a different outbound type (like User Defined Routing) and have a replacement plan in place.

Quick Q&A #

Why did this appear even though I didn't deploy any LoadBalancer-type Services?
That's totally normal! AKS provisions this LoadBalancer by default to manage the cluster's essential outbound traffic and infrastructure health checks—you don't need to deploy any services for it to show up.

内容的提问来源于stack exchange，提问作者Tarun Kukreja