AKS [Feature] Fleet - customize resource group name

When using creating a Kubernetes fleet manager, it creates two additional RG, one FL_ for hosting the hub cluster and one FL_MC_ for hosting the resources of the hub.

Describe the solution you'd like The same feature as --node-resource-group parameter, the capacity to specify the generated resource group name(s).

Describe alternatives you've considered None and it's a real issue when the customer implements naming policies

something like. next question, do we need two resources groups ? why can't the hub either in the first one, or the MC one ? az fleet create --resource-group ${RESOURCE_GROUP} --name ${FLEET_NAME} --location westeurope --node-resource-group

Nov 05 '22 20:11 lgmorand

We considered fleet resource groups as fully managed resource by fleet. Therefore, we plan to exempt those resource groups from customer policies (instead of allowing users to set their own resource group names).

Let us know if you have any feedback upon the directions we are taking.

Jan 11 '23 21:01 circy9

Hi Liqian

IMHO you are doing it the wrong way then :) explain how it differs from the the MC_ RG created with an AKS which is visible, not exempted of policies and allows the Cx to choose the name ?

Bypassing Cx policies is not the way how we should do it (FSI customers don't like that, trust me). Imagine the customer POV, ALL RG have a naming convention and then, one rogue RG name decided by fleet.

I don't say it's a top priority feature (far from that) but Fleet creates AKS cluster as hub, we should expect the same behavior. Does it use the same CRP api to create the hub cluster because there, effort should me not too big.

Thanks

Jan 12 '23 10:01 lgmorand

Action required from @Azure/aks-pm