Azure Container Apps (Consumption Plan) MC_ autogenerated Load balancer not configured - Stack Overflow

admin管理员组

文章数量:1400123

In the last few days when I've started to provision new Container App Environments the autogenerated MC_ resources are not getting setup correctly. They are missing nearly all config, which means my container apps are not reachable from the internet.

I'm using bicep to provision it. The Container App Environment is on a VNet. It's provisioning everything correctly in the target resource group. All the apps start up and are working and talking to each other inside the VNet.

However.. The autogenerated MC_ resource group Azure makes in the background that has the load balancer and public Ip's is not getting configured correctly. Here is what it looks like:

Incomplete setup

Whereas a working one that was setup a couple of weeks ago looks like this:

Working Setup

Has anyone else seen this happening or have any idea how to get Azure to re-create this or fix it? I've tried to mirror the setup from the working one but I don't know how to find the correct internal port for the health check probes for the kubernetes it's using behind the scenes.

In the last few days when I've started to provision new Container App Environments the autogenerated MC_ resources are not getting setup correctly. They are missing nearly all config, which means my container apps are not reachable from the internet.

I'm using bicep to provision it. The Container App Environment is on a VNet. It's provisioning everything correctly in the target resource group. All the apps start up and are working and talking to each other inside the VNet.

However.. The autogenerated MC_ resource group Azure makes in the background that has the load balancer and public Ip's is not getting configured correctly. Here is what it looks like:

Incomplete setup

Whereas a working one that was setup a couple of weeks ago looks like this:

Working Setup

Has anyone else seen this happening or have any idea how to get Azure to re-create this or fix it? I've tried to mirror the setup from the working one but I don't know how to find the correct internal port for the health check probes for the kubernetes it's using behind the scenes.

• azure
• azure-aks
• azure-container-apps

Share Improve this question Follow asked Mar 25 at 8:24 Intrepid DeveloperIntrepid Developer 1 4

• have you tried deleting the non working one and recreate ? – Thomas Commented Mar 25 at 8:45
• Yep, first thing I tried. No luck though each time it re-provisions it the mappings are all missing. It was working fine last week and nothing has changed other than the name of the environment, really odd. – Intrepid Developer Commented Mar 25 at 9:04
• 1 Must have been a transient issue in Azure. The deployment is now magically working again on the most recent provision attempt... – Intrepid Developer Commented Mar 25 at 15:08
• goo to hear that it is resolved. – Thomas Commented Mar 25 at 18:40

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

I do agree with Thomas' point and am posting the solution for the community's benefit. If anyone is having the same issue, they can resolve it with the posted answer.

• There can be temporary issues or delays in resource creation. These errors may be due to background processes that might not be completed properly or network congestion.

• When resources like the MC_ resource group, load balancers, and public IPs aren't set up correctly, it could be due to a transient error. In many cases, this type of error can be resolved by retrying the deployment process.

Reference: https://learn.microsoft/en-us/azure/container-apps/revisions

https://azure.status.microsoft/en-us/status

本文标签： Azure Container Apps (Consumption Plan) MC autogenerated Load balancer not configuredStack Overflow