concept frontend IP pool in category azure

appears as: frontend IP pool, The frontend IP pool
Learn Azure in a Month of Lunches, Second Edition

This is an excerpt from Manning's book Learn Azure in a Month of Lunches, Second Edition.

Figure 8.1 Traffic from the internet enters the load balancer through a public IP address that’s attached to a frontend IP pool. The traffic is processed by load-balancer rules that determine how and where the traffic should be forwarded. Health probes attached to the rules ensure that traffic is distributed only to healthy nodes. Then a backend pool of virtual NICs connected to VMs receives the traffic distributed by the load-balancer rules.
  • To create a load-balancer NAT rule, define a name, such as natrulessh, and the frontend IP pool to use. The NAT rule examines traffic on a given protocol and port, such as TCP port 50001. When there’s a rule match, the traffic is forwarded to backend port 22:
  • az network lb inbound-nat-rule create \
      --resource-group azuremolchapter8 \
      --lb-name loadbalancer \
      --name natrulessh \
      --protocol tcp \
      --frontend-port 50001 \
      --backend-port 22 \
      --frontend-ip-name frontendpool

    A public IP address has been assigned to the frontend IP pool, and you created a health probe to check the status on a custom health page for a web server. A load-balancer rule was created to distribute web traffic from your customers to a backend pool; the rule uses the health probe. You also have a load-balancer NAT rule that permits SSH traffic, but there are no VMs to receive that traffic yet. Your pizza-store customers are hungry, so let’s create some VMs that can run your web application and to which the load balancer can distribute traffic!