0

When a new Kubernetes service is created in Azure a new resource group with a similar name to the cluster is also created. In this "resource group" all the disks etc. which are created from Kubernetes are stored. Is there a way I can avoid that this sub-resource group is created and that all resources created from Kubernetes are put in the resource group where the cluster is located?

The background is that our Ops team would like to structure the resource groups and therefore the generated resource group structure is not preferred. Note that the information that this is not possible or at least not without a significant amount of effort would also be very useful for me.

Improve this question
1
  • Same issue here, I find it rather confusig since I expected that the kubernetes service (AKS cluster) should be listed in the new resource group along with the disks etc. Also when performing managing tasks with az command, the resource group name for ie. disk is mc_<resource-group-name>_<resource-group-name>_<region-name> Commented Jan 13 at 15:52

1 Answer 1

Reset to default
1

According to the documentation, you can't create the cluster resources inside the resource group where the cluster is located. The only option available is to provide a name for the second resource group at cluster creation.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.