I hope I was able to answer your questions. It is important to note that the number of SNAT ports will still be determined by the number of backend instances in the VMSS, regardless of the number of public IP addresses you have. This allows you to have two public IP addresses available for your AKS cluster. Additionally, you can create a separate public IP resource and associate it with the same standard load balancer. You can create a standard load balancer in Azure and assign the default public IP to it. Regarding your second question, it is indeed possible to use the default public IP automatically created by Azure and add another public IP of your own. The availability of SNAT ports is tied to the number of backend instances, not the number of IP addresses.
If you have two backend instances, the total SNAT port count will be 128,000 (64,000 per instance).Īdding multiple IP addresses as outbound rules in the AKS standard load balancer targeting the same backend pool does not directly increase the SNAT port count. So, if you have a single backend instance in your VMSS, you will have 64,000 SNAT ports available. The allocation of SNAT ports in Azure is based on the number of backend instances in the VMSS, with each instance having access to 64,000 SNAT ports. The number of SNAT ports in Azure is determined by the number of backend instances in the VMSS. Adding more IP addresses to a Standard Load Balancer in an AKS VMSS does not directly increase the number of SNAT ports available.
0 kommentar(er)
