This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 68%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
Hello,
As mentioned here, we can specify the ip address for internal load balancer but, is it possible to specifically keep that ip only for load balancer so that other resource cannot occupy it.
For eg. if for some reason we delete this internal load balancer service and within that moment a new pod or a new node in AKS(with Azure CNI networking) is created then its highly likely that they will occupy the ip address.
How to keep that internal subnet ip specifically for internal load balancer?
Kind Regards,
Tanul
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 30%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAB%3C/text%3E%3C/svg%3E)
Hello Tanul
The IP address assignment in a subnet is incremental, for example, if you have Azure CNI and one node using 10.224.0.4 - 10.224.0.32, you can't reserve 10.224.0.33. If you create a new node, the IPs for that node will start with 10.224.0.33. It is not possible to keep specific IPs unassigned. The only workaround I think of is to have a resource that would use that IP, remove it, and then create the internal load balancer with "service.beta.kubernetes.io/azure-load-balancer-ipv4: <IP>" annotation.
You may consider opening a feature request here: https://github.com/Azure/AKS/issues
If you have additional questions, please let us know in the comments.
If this has been helpful, please take a moment to accept answers as this helps increase visibility of this question for other members of the Microsoft Q&A community. Thank you for helping to improve Microsoft Q&A!
@Andrei Barbu , Got it.. Thanks.. I'll do one thing.. I'll pick the ip from the last 5 free ip addresses in subnet. In that way its highly likely that I can easily get it in such scenarios.
Yes, that's a smarter idea. Just one extra note about these five IP addresses reserved per each subnet:
https://video2.skills-academy.com/en-us/azure/virtual-network/virtual-networks-faq#are-there-any-restrictions-on-using-ip-addresses-within-these-subnets
@Andrei Barbu , Yup I'm aware of that. When we create subnet Azure automatically reserves it. For eg. if we create /22 subnet, Azure portal automatically shows that we have 1019 ip's available.