Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can the following RG be found? I'm seeing errors when building this stack as it cannot find this RG #12

Open
ardeshir opened this issue Apr 12, 2024 · 1 comment

Comments

@ardeshir
Copy link


resource loadBalancer 'Microsoft.Network/loadBalancers@2021-05-01' existing = {
  name: 'kubernetes-internal'
  scope: resourceGroup(containerAppsManagedResourceGroup)
}

ERROR: deployment failed: failing invoking action 'provision', error deploying infrastructure: deploying to subscription:

Deployment Error Details:
ResourceGroupNotFound: Resource group 'MC_nicefield-8217ac6e-rg_nicefield-8217ac6e_eastus' could not be found.

TraceID: 42deee2e3a098989afaab3fb0bcb1ada

If you can explain what containerAppsManagedResourceGroup is trying to reach, maybe there can be a work around?
Thank you for this repo, and any future help you can provide!

@sebafo
Copy link
Owner

sebafo commented May 2, 2024

I have described it here: microsoft/azure-container-apps#402 (comment)

To deploy AFD with a private ACA environment you need to create a private link connection between Front Door and the internal Azure Load Balancer. For that reason you have to create a Private Link Service for the Load balancer.
The challenge is now to 'find' the Load Balancer the Private Link Service should be created for and add the ID of the Load Balancer to the Private Link Service resource.
In my example I used the default domain of the environment to create the name of the 'auto-generated' resource group, because you need to provide the name and the resource group of the Load Balancer to get the required ID.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants