`infrastructureResourceGroup` is null for Consumption environments

[cailyoung]

Please provide us with the following information:

This issue is a: (mark with an x)

• [x] bug report -> please search issues before submitting
• [ ] documentation issue or request
• [ ] regression (a behavior that used to work and stopped in a new release)

Issue description

A clear and concise description of the observed issue.

Steps to reproduce

1. Create an environment without specifying an infrastructure resource group
2. az containerapp env show the environment

Expected behavior [What you expected to happen.] infrastructureResourceGroup has the resource group containing the load balancer

Actual behavior [What actually happened.] infrastructureResourceGroup is null in the response

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context

Ex. Did this issue occur in the CLI or the Portal?

[Seris370]

May I confirm if you have created a workload profile environment with custom vNet? You can check the workloadProfiles section and the vnetConfiguration section in the environment response.

[cailyoung]

@Seris370 no, we use consumption profile. I'm trying to locate the load balancer that gets created in the MC_* resource group.

[Seris370]

Hi @cailyoung , the infrastructureResourceGroup is only available and customizable for workload-profile environments. For consumption-only environments, the resource group that holds the local balancer has the default name of an AKS node resource group, MC_<AksClusterName>-rg_<AksClusterName>_<Region>, for example MC_salmonbay-a00b24c4-rg_salmonbay-a00b24c4_centralus. You can get the AKS cluster name from the defaultDomain property of the container apps environment.

[cailyoung]

@Seris370 thanks for clarifying that. It would be good to have the API docs and/or product documentation clarified so that the pattern for naming the resource group was documented.