Azure Cloud - Ingress High Availability


The network load balancer that can be deployed in the Azure Cloud fits the architecture and features we are looking for as described in this article Ingress High Availability in Public Clouds . More details in Microsoft Documentation can be found at this link for those interested

Automated deployment into your Resource Group using Arm Template is described in 
this Github repo

Important Notes: 

Add the following rule to the ufw to allow in healthcheck probes, because the source IP is not the LB Frontend IP.

sudo ufw allow in to any port {#} proto {type} from

If you need public IPs to be assigned to your backend ERs, then you need the standard SKU type for the Public IP resources. Otherwise, you will need to remove them and use NAT Instance to reach internet.


Configuration Steps:

  1. Log into the Azure Cloud Console

  2. Navigate to home page and enter Load Balancer in the search area at the top of the screen

  3. Click on “Create Load Balancer” (Microsoft Load Balancer)

  4. Fill in the options as desired but the Type must be Internal.

  5. Hit “Review+create”

  6. Navigate to the LB Main Menu and add backend pool

  7. Fill in the details and add ERs to it

  8. Navigate to the health probes menu and hit the add button

  9. Fill in the details as required and hit the add button.

  10. Navigate to the LB main menu and add load balancing rules

  11. Fill in the details as required and hit the add button

    1. Select HA ports required

    2. Session persistence - selection depends on which type of load balancing hash algorithm is required

    3. Floating IP and TCP Reset disabled

  12. Update the routing table to point to the LB Front End Private IP for routes to be sent over NetFoundry Network.mceclip0.png

  13. Repeat this step for  every route you want to point to the load balancer.
Was this article helpful?
3 out of 3 found this helpful



Please sign in to leave a comment.