Azure / AKS

Azure Kubernetes Service
https://azure.github.io/AKS/
1.97k stars 307 forks source link

Pod creation failing with "no available addresses" #2532

Closed elan-wrussell closed 2 years ago

elan-wrussell commented 3 years ago

What happened: Within a node pool pods are stuck at ContainerCreating with the event:

Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "ce54c8f820d18e4ea9eca3b7da6482d110f162a4b0bc03a905a33fb2712b1e4d": Failed to allocate pool: Failed to delegate: Failed to allocate address: No available addresses

What you expected to happen: Nodes should run as per normal.

How to reproduce it (as minimally and precisely as possible): Unfortunately it is happening randomly and the only resolution appears to be to delete and recreate the pool.

Anything else we need to know?: The cluster is using Azure CNI and a private subnet (/21 allocation) and currently showing 1701 available IPs. The max pod limit if all node pools were scaled to max and max pods allocated would be 530.

Environment:

ghost commented 3 years ago

Hi elan-wrussell, AKS bot here :wave: Thank you for posting on the AKS Repo, I'll do my best to get a kind human from the AKS team to assist you.

I might be just a bot, but I'm told my suggestions are normally quite good, as such: 1) If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster. 2) Please abide by the AKS repo Guidelines and Code of Conduct. 3) If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics? 4) Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS. 5) Make sure there isn't a duplicate of this issue already reported. If there is, feel free to close this one and '+1' the existing issue. 6) If you have a question, do take a look at our AKS FAQ. We place the most common ones there!

ghost commented 3 years ago

Triage required from @Azure/aks-pm

ghost commented 3 years ago

Action required from @Azure/aks-pm

ghost commented 3 years ago

Issue needing attention of @Azure/aks-leads

ghost commented 3 years ago

Hi there :wave: AKS bot here. This issue has been tagged as needing a support request so that the AKS support and engineering teams have a look into this particular cluster/issue.

Follow the steps here to create a support ticket for Azure Kubernetes Service and the cluster discussed in this issue.

Please do mention this issue in the case description so our teams can coordinate to help you.

Thank you!

ghost commented 3 years ago

Case being worked with Microsoft Support, adding stale label for automatic closure if not other reports are added.

ghost commented 2 years ago

This issue will now be closed because it hasn't had any activity for 15 days after stale. elan-wrussell feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.