Support for not being forced to stay with the initial name of the default_node_pool in azurerm_kubernetes_cluster

[timdeluxe]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

In azurerm_kubernetes_cluster it is required to provide the configuration of a default_node_pool including a name. But one has to stay forever with that name, because this happened:

• added a new nodepool with aks cli
• migrated all pods to new nodepool by draining nodes of initial nodepool
• changing mode of new nodepool to system and initial nodepool to user
• deleted initial nodepool
• (aks is absolutely happy at this point)
• changed terraform code to give the "default_node_pool" the name of the new nodepool by changing the value of parameter "name"
• ran terraform and got this Error: flattening `default_node_pool`: The Default Agent Pool "default" was not found

So i was forced to create a further nodepool named "default" and move all pods again (and the rest of the steps), just to make terraform happy. This is somewhat crazy.

New or Affected Resource(s)

• azurerm_kubernetes_cluster

Potential Terraform Configuration

Note: I do not expect code to be changed. It is fine. I understand that the default_node_pool needs to be there (found explanation here: #7686 (comment)). But i would like terraform to respect the change of its name, which happened outside of terraform.

References

• Make default_node_pool in azurerm_kubernetes_cluster optional #7686 (comment)
• https://docs.microsoft.com/en-us/azure/aks/use-multiple-node-pools
• https://docs.microsoft.com/en-us/azure/aks/use-system-pools

[ghost]

This has been released in version 2.29.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.29.0"
}
# ... other configuration ...

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!