aks node pool upgrade and hitting SubnetIsFull

AKS cluster node upgrade a control by the maxsurge parameter.  If case your subnet have limited ip to spare then the cluster might end up with ''subnetIsFull' error. This is a hard problem to resolve because 

1. Probably can't reduce or scale down your cluster size to gain additional IP address. 

2. Creating a new subnet and placing your node pool might not be possible as your cluster is on a managed cluster. 

3. To extend the size of your AKS subnet cluster would requires alot of work. These are the steps requires to extend your subnet.

1- Stop the AKS cluster

2- Delete all the VMSS (nodepools) from the MC resource group. (to release all the attached NICs from the subnet)

3- Delete the old subnet

4- Create a new subnet with the same name as the old subnet and a different IP range.

5- Start the cluster

This will be a WTH moment. 

https://learn.microsoft.com/en-us/answers/questions/1295498/resize-aks-managed-subnet

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