Azure Load Balancer

this topic explains how to use an azure load balancer (layer 4) for your turbine deployment architecture diagram load balancer create a https //docs microsoft com/en us/azure/load balancer/quickstart load balancer standard public portal type must be set to public because internal load balancers do not support hairpinning continue setup of the load balancer with the following settings resource group should be set according to your organization's standards region should match that of the virtual machines that turbine will be installed in type set to public this has to be set to public because internal load balancers do not support hairpinning access to the virtual machines should still be restricted by network security groups sku set to standard tier set to regional public ip address can either be a new public ip address to use or select an existing one availability zone set to zone redundant backend pools create the following backend pools port 443 backend pool configuration set to nic ip version set to ipv4 virtual machines add the first virtual machine that you'll be running the turbine platform installer on to the backend pool after turbine has been installed on the additional nodes they need to be added to this target group port 8800 backend pool configuration set to nic ip version set to ipv4 virtual machines add the first virtual machine that you'll be running the turbine platform installer on to the backend pool after turbine has been installed on the additional nodes they need to be added to this target group port 6443 backend pool configuration set to nic ip version set to ipv4 virtual machines add the first virtual machine that you'll be running the turbine platform installer on to the backend pool after turbine has been installed on the additional nodes they need to be added to this target group optional port 80 used for the http to https redirect and can be excluded if you only want https/443 to be available backend pool configuration set to nic ip version set to ipv4 virtual machines add the first virtual machine that you'll be running the turbine platform installer on to the backend pool after turbine has been installed on the additional nodes they need to be added to this target group health probes create the following health probes port 443 protocol set to tcp port set to 443 interval and unhealthy threshold may vary based on your preferences for how quickly a virtual machine should become unhealthy in order to stop receiving traffic port 8800 protocol set to tcp port set to 8800 interval and unhealthy threshold may vary based on your preferences for how quickly a virtual machine should become unhealthy in order to stop receiving traffic port 6443 protocol set to tcp port set to 6443 interval and unhealthy threshold may vary based on your preferences for how quickly a virtual machine should become unhealthy in order to stop receiving traffic optional port 80 used for the http to https redirect and can be excluded if you only want https/443 to be available protocol set to tcp port set to 80 interval and unhealthy threshold may vary based on your preferences for how quickly a virtual machine should become unhealthy in order to stop receiving traffic load balancing rules create the following load balancing rules port 443 ip version set to ipv4 frontend ip address set to the ip that was chosen when the load balancer was created protocol set to tcp port set to 443 backend port set to 443 backend pool set to the port 443 backend pool created above health probe set to the port 443 health probe created above floating ip set to disabled outbound source network address translation set to outbound and inbound use the same ip port 8800 ip version set to ipv4 frontend ip address set to the ip that was chosen when the load balancer was created protocol set to tcp port set to 8800 backend port set to 8800 backend pool set to the port 8800 backend pool created above health probe set to the port 8800 health probe created above floating ip set to disabled outbound source network address translation set to outbound and inbound use the same ip port 6443 ip version set to ipv4 frontend ip address set to the ip that was chosen when the load balancer was created protocol set to tcp port set to 6443 backend port set to 6443 backend pool set to the port 6443 backend pool created above health probe set to the port 6443 health probe created above floating ip set to disabled outbound source network address translation set to outbound and inbound use the same ip optional port 80 ip version set to ipv4 frontend ip address set to the ip that was chosen when the load balancer was created protocol set to tcp port set to 80 backend port set to 80 backend pool set to the port 80 backend pool created above health probe set to the port 80 health probe created above floating ip set to disabled outbound source network address translation set to outbound and inbound use the same ip network security groups for azure load balancers, ingress port access is defined in the network security groups used by the virtual machines and subnets the port requirements are available in system requirements, docid 9lxricxlm1t14ydlkt4zr turbine configuration be sure to enable the enable the ingress controller option on the turbine platform installer ui config tab