Added support for custom resource group name in AKS #3869
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I wanted to use Terraform for my project, but I found one particular thing missing - lack of possibility to enter a custom name for a node resource group in Azure Kubernetes Service. To make a long story short - by default, AKS creates an additional resource group holding all the infrastructure resources and keeping them separate from the managed cluster. That RG has a dummy name what makes following naming conventions difficult. This is why Microsoft added a
nodeResourceGroup
parameter in the 2019-04-01 API version.From my investigation, Terraform supports that parameter but only as an output. This PR adds support for
nodeResourceGroup
by introducing acustom_node_resource_group
parameter. I did not usenode_resource_group
name as it was already added as a computed result of running an AKS deployment.Kamil