It might be worth calling out that AKS generates another resource group to dump the cluster-related resources.
Assuming that people are new to AKS and will use the portal and/or CLI and inspect their resources, this could throw them off.
This could also be useful for users who have specific requirements around audibility, or have a specific way to manage billing etc (like by tagging resources, or some custom pattern). Customers may also use specific naming conventions for RG names.
It might be worth calling out that AKS generates another resource group to dump the cluster-related resources.
Assuming that people are new to AKS and will use the portal and/or CLI and inspect their resources, this could throw them off.
This could also be useful for users who have specific requirements around audibility, or have a specific way to manage billing etc (like by tagging resources, or some custom pattern). Customers may also use specific naming conventions for RG names.