Why is my Container App Environment taking so long to deploy?

0
9
Asked By TechieGamer93 On

Hey everyone,

I've been trying to deploy a Container App Environment using Bicep, but it's been running for about 1 hour and 29 minutes, and I still don't see any progress in the Activity log. These environments are set up within a virtual network (vnet), and I noticed that some resource groups were created and then deleted during the process.

The resource names look like this: MC_jollyfield-***-rg_jollyfield-***_australiaeast. I'm guessing these are tied to the Kubernetes cluster environment associated with my app container setup. Also, I'm wondering if there's an issue with my managed certificate configuration. It might be best to cancel the deployment for now and remove the certificate because I recall a bug related to this from about a year ago.

To give some background on my solution, I managed to resolve similar issues in the past by adding a workload profile set to consumption, and linking it to the relevant infrastructure resource group. This also required creating delegation subnets in the vnet for the container app environments. If managed certifications are involved, I've faced scenarios where it becomes complex, so I typically create the app environment and containers first without cert bindings, and then handle the bindings as a separate step in my CI process.

4 Answers

Answered By VMWarrior23 On

I gave up on container apps and functions due to complications like this. I find deploying to a VM is much easier, though I understand that might not work for everyone.

Answered By DevWizard99 On

If it’s taking longer than 10 minutes and you aren't seeing logs, it could be a permissions issue. You might want to double-check those settings.

Answered By CloudGuru88 On

Deployments for Azure environments can take a long time, sometimes even experiencing delays. It’s normal for them to take a full lifetime to complete, so don’t stress too much if it seems like it's taking forever.

Answered By AzureNinja42 On

Do you have Private Links set up in your deployment? I had similar issues once, and the delay was because the private links weren’t approved on the target resource. Also, if you’re configuring a new Container App, make sure that the image in your Azure Container Registry (ACR) is healthy; sometimes if the image isn’t ready, it stalls the entire deployment.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.