filip
filip

Reputation: 1513

AKS template creates new resource groups

When I create an AKS cluster using Azure portal I can see that new resource groups are created. It seems that I have no control over how they are named, especially the one with with "MC_" prefix. I also don't see an option to change its name when using ARM template.

In addition, if I create a cluster in customer's subscription, where I only have access to 1 resource group, I don't even see the newly created RG and can't manage it.

Is there a way to force deployment of all AKS components into a single resource group?

Upvotes: 1

Views: 1019

Answers (1)

4c74356b41
4c74356b41

Reputation: 72191

No, there is no way to force it at this point in time. As for the access, you should request access to that RG. No real workarounds.

Secondary resource group name can be inferred, I think, its something like:

MC_original-resource-group-name_aks-resource-name_location

it also creates OMS resource group (if you enable OMS) and Network Watcher (this can be disabled, btw, but its a provider setting). you have no control over that as well.

there is a not implemented yet nodeResourceGroup property: https://learn.microsoft.com/en-us/rest/api/aks/managedclusters/createorupdate#examples

EDIT: this is actually working right now, so the nodeResourceGroup property can be used. But it would still be a new resource group, so you would still need to request access to that group and using this property is not possible with the portal (so ARM Templates\pulumi\terraform)

Upvotes: 3

Related Questions