I've been using Bicep to deploy my Container App Environment, and it's been stuck running for an hour and a half now. I don't see any updates in the Activity log, so I'm a bit concerned. The environments are set up within a VNet, and I noticed something odd: some resource groups were created and then deleted. They have names like 'MC_jollyfield-***-rg_jollyfield-***_australiaeast,' which I assume are related to the Kubernetes cluster for my app container environment.
I suspect there might be an issue with my managed certificate setup. I'm thinking about canceling the deployment for now, removing the certificate, and adding it later since I remember there being a bug related to this a year ago.
To address the problem, I found that I need to add a workload profile and specify it as consumption. This also allows me to set the resource group for the underlying infrastructure. I also have to create delegation subnets in the VNet for the container app environments. If managed certificates are involved, it could lead to a chicken and egg situation, so I'm planning to create the app environment and containers first, without the certificate binding, and validate later as part of my CI process.
3 Answers
Yeah, I've noticed that deployments for Azure environments can really drag on sometimes. Sometimes it takes longer than expected, especially if resources like Private Links are involved. If they're not approved, it can delay things. Also, make sure the image you're using is healthy in the Azure Container Registry; if it's not available, that could keep the deployment hanging too!
Honestly, I stepped away from using container apps because of long waits like this. Switching to VMs has made my life so much easier. But I get that it might not be ideal for everyone. Just keep an eye on those logs!
If the deployment is taking over 10 minutes and you're not getting logs, it might be a permissions issue. Check that you have adequate permissions for all the resources you're interacting with. Sometimes that's the silent culprit behind slow deployments!
Thanks for the tip! I think it might be something in my Bicep code that's causing the holdup. I've updated the initial post with the details.