AKS
AKS copied to clipboard
Azure
ACN allocated ip addresses not visible in portal
Hiya,
I'm currently using the acn.azure.com crd with a node subnet and a pod subnet.
The node subnet is behaving as expected. I've got 4 nodes up and running and I can see them as connected devices in portal. The pods also show that they're using the correct pod subnet
however the pod subnet in portal don't show them as connected devices and still consider them as available ips when I run:
az network vnet check-ip-address --ip-address 10.111.17.80
{
"available": true,
"availableIpAddresses": null,
"isPlatformReserved": false
}
Is this expected behaviour of a subnet with a Microsoft.ContainerService/managedClusters delegation?
Hi helenanorback, 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:
- If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster.
- Please abide by the AKS repo Guidelines and Code of Conduct.
- If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics?
- Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS.
- 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.
- If you have a question, do take a look at our AKS FAQ. We place the most common ones there!
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
![microsoft-github-policy-service[bot] avatar](https://avatars.githubusercontent.com/in/95686?v=4 "Published by a pub.dev verified publisher"){kind=small}
Triage required from @Azure/aks-pm no assignees