<p>In <a href="https://kubernetes.github.io/ingress-nginx/deploy/baremetal/" rel="nofollow noreferrer">https://kubernetes.github.io/ingress-nginx/deploy/baremetal/</a>
In metalLB mode, one node attracts all the traffic for the ingress-nginx
By node port we can gather all traffic and loadbalance it podes by service</p>

<p>what is diffrence between node port and metalLB?</p>

<p>A Nodeport offers access to a service through a port on the node (hence node+port). A port is allocated that you can access the service through on any node in the cluster.</p>
<p>MetalLB is a load balancer for on-prem clusters. It allocates services with separate dedicated IP addresses allocated from a pool. So, if you want to access a service (an ingress controller or something else) on a dedicated IP then MetalLB allows you to do this.</p>
<p>MetalLB works in two ways, either BGP or Layer2 ARP. The latter is easier to set up if you're working on a &quot;lab&quot; environment. Basically the MetalLB responds to ARP requests sent by clients trying to connect to a service to which it's allocated an IP.</p>
