I have a resource group with a virtual network in Azure. The virtual network has subnets, but they are not appearing in the list, nor are they returned by the following cloud shell line:
az network vnet subnet list --vnet-name [vnet] --resource-group [resource group]
You would think that this is because they do not exist. However, one of these subnets has a load balancer, and two more have running containers in them. These resources are all still working. I can still access the containers through the load balancer, and the containers still have the same private IP addresses as before.
Furthermore, I can create create a new subnet with the same address space and Azure does not raise any errors or objections, then delete that subnet, and the load balancer and containers are still running just fine.
I think the problem may have been created when I created a new virtual machine in a fourth subnet of this network that had already been Delegated to ContainerInstance. You would think that Azure would throw an error and not let me do that, for everything else it complains about, but here we are.
Is there some kind of orphan virtual network that these subnets are in now? How do I troubleshoot this?