Hello,
I've recently created a container instance deploying it to an existing virtual network with an only one subnet, since the creation of a container instance change the delegation of the subnet the problem is that I'm not able to attach that subnet to other resources using the same virtual network due to delegation problem.
My scenario is:
- The subnet in the virtual network use the whole address space of the virtual network (this is because we did not think about adding any other resources but virtual machines)
- I wanted to deploy a container but had to change subnet's delegation and move the resources connected to the subnet
- I wanted to change the addresses prefix so that I would be able to create more subnets but obtained an error from the Azure portal telling me that the subnet is being used by a resource (container)
- Removed the container and tried again to change addresses prefix of previous subnet
- Received the same error (subnet is being used by a resource) even though I've deleted the container
My question is do I have to delete the Virtual Network and recreate it (using different subnets) or there's a way to update the just the subnets configuration?
Thanks in advance for you answers,
Greetings,
Raffaele Piccolo