Experienced an issue yesterday and today where multiple running containers end up with the same external IP address assigned to them. The IP address works to call into one of the containers and the other is left without inbound network access.
The containers were created around the same time. I have 6 VSTS release environments that each create 20 containers through an ARM template. The 6 environments are all triggered at the same time to deploy. I use 2 different subscriptions and 3 resource groups within each subscription (1 for each supported aci region). In total trying to create 120 containers.
The containers in the example attached with the same IP were created in different azure subscriptions but both in West Europe.
Hi,
Experienced an issue yesterday and today where multiple running containers end up with the same external IP address assigned to them. The IP address works to call into one of the containers and the other is left without inbound network access.
The containers were created around the same time. I have 6 VSTS release environments that each create 20 containers through an ARM template. The 6 environments are all triggered at the same time to deploy. I use 2 different subscriptions and 3 resource groups within each subscription (1 for each supported aci region). In total trying to create 120 containers.
The containers in the example attached with the same IP were created in different azure subscriptions but both in West Europe.
Thanks
Nathan