1

Azure Container/Kubernetes Service - Virtual Network : IPs and network interface are not deleted/cleaned after pods deletion.

No more available address in the subnet that kubernetes use after a few deployments.

Is there a way to clean those network interface?

goodguytrigu
  • 456
  • 2
  • 13
  • 1
    what's the Kubernetes version? This used to be a problem in acs-engine/azure-cni but it should be long fixed in AKS ([reference](https://github.com/Azure/azure-container-networking/issues/76)) – Alessandro Vozza Nov 13 '18 at 21:35
  • Shouldn't you delete the deployment of the pods? Maybe I do not really understand it. – Charles Xu Nov 14 '18 at 14:09
  • @alev: the kubernetes version is 1.11.13 – goodguytrigu Nov 14 '18 at 17:52
  • @CharlesXu-MSFT This problem occurs when I delete a namespace or a specific deployment, AKS does not remove the network interfaces related to the namespace or the deployments/pods. – goodguytrigu Nov 14 '18 at 17:53

2 Answers2

2

RESOLVED: By default, AKS is reserving 31 ips for each node in the cluster so my problem was not that the IPs were not released but just that a lot of IPs were reserved :)

goodguytrigu
  • 456
  • 2
  • 13
0

You can try and see if you can:

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • @VonC I used the script from script to find and delete unattached network interface but the problem is that those network interfaces are still connected to the VMs that belongs to the AKS cluster. AKS should be the one freeing the network interfaces after a deletion happen in the cluster... – goodguytrigu Nov 13 '18 at 21:22
  • @Ben Strange. May be this is an ownership issue? (as in https://github.com/Azure/AKS/issues/427#issuecomment-397368508) – VonC Nov 13 '18 at 21:36