Support for accessing data about single AKS cluster node pool

[jmcshane]

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

Move the agent_pool_profiles field out of the azurerm_kubernetes_cluster data source into its own field, corresponding to the way that the resources are managed after the changes in #4899.

New or Affected Resource(s)

• azurerm_kubernetes_cluster_node_pool

Potential Terraform Configuration

data "azurerm_kubernetes_cluster_node_pool" "example" {
  name                  = "internal"
  kubernetes_cluster_id = data.azurerm_kubernetes_cluster.example.id
}

Returns spec similar to the agent_pool_profiles in the current azurerm_kuberenets_cluster data source now.

References

• r/kubernetes_cluster: supporting conditional updates / introducing default_node_pool #4898

[maarek]

@jmcshane Sorry, I didn't get a moment to write this up, so thanks for getting ahead of me.

Currently, another team creates the AKS clusters through some automated process of their own and then hands them off to the development teams to manage afterwards. This means that when an AKS cluster is done being provisioned, I am required to import it into my own terraform script.

The first thing that my script does to maintain state is to fetch the currently state of a cluster resource and then substitutes those values into the azurerm for things that my team does not control. This allows me to not have to manage all of the details of the cluster but only certain things such as node count, kubernetes version, and plugins.

My question in #4898 stemmed from the inconsistency between the naming where my data source was named differently than the new default_node_pool naming in azurerm. There is some discussions about whether the node pools will be created by the development team or not, but adding this data source would be helpful in a similar way as the cluster resources that I mentioned above.

[ghost]

This has been released in version 2.14.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.14.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!