Resolving AKS SNAT issue by increasing allocation of ports to nodes

 I think two suggestion might work 

1. Increasing the number of ports allocated to nodes from 1024 to something higher. Technically, I think this can be an improvement feature - if we haven't max out the nodes - then we can get some more ports allocated to nodes. 

2. Decreasing the idle timeout of connection from 30 to maybe 20 minutes. 

Anyways, I end up using the given formula to increase my port number slightly. So 

((64000 / 1056) x number of IP) = number of nodes that can live in your AKS cluster - 1

This 1 is for surge nodes. That's the default surge value. 

For example, 

((64000 / 1056) x 2 => 120 nodes - 1 (surge) => 119 nodes that you can have in your cluster.

References

https://learn.microsoft.com/en-us/azure/aks/load-balancer-standard#configure-the-allocated-outbound-ports

Comments

Post a Comment

Popular posts from this blog

The specified initialization vector (IV) does not match the block size for this algorithm

Image
If you're getting  exception when trying to assigned key to a symmetric key and getting error message below :- The specified initialization vector (IV) does not match the block size for this algorithm And your code probably look like something below :- Then you need to go into debug mode and start looking into the supported size for IV as shown in diagram below :- As you can see, IV is 16 bytes, so you need to provide 16 bytes. The same goes for Key field too, if you're adding anything to it. As long as you provide a valid key size, then we're good and you're code will be ready.
Read more