Terraform-provider-azurerm: add export/out for azurerm_kubernetes_cluster

Created on 4 Apr 2020  ·  5Comments  ·  Source: terraform-providers/terraform-provider-azurerm

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

would be great (extermely useful!) to have azurerm_kubernetes_cluster export a list of the VM hostnames of all the VM hosts that were created as part of the cluster creation. This would be used for node affinity purposes.

New or Affected Resource(s)

azurerm_kubernetes_cluster

Potential Terraform Configuration

Where we'd be able to use this export/output:

output "vmhosts" {
    value = azurerm_kubernetes_cluster.vm_hosts
}
duplicate question servickubernetes-cluster

Most helpful comment

+1 to exporting identityProfile.kubeletidentity.clientId, it is needed when installing AAD Pod Identity on AKS Clusters with Managed Identity enabled.

All 5 comments

Another one: identityProfile.kubeletidentity.clientId is an attribute of the AKS cluster, but is currently not available to be exported as an output. This is another item that would be extremely useful as a terraform output. (yes in my case, for exact same purpose of using with AAD Pod Identity)

+1 to exporting identityProfile.kubeletidentity.clientId, it is needed when installing AAD Pod Identity on AKS Clusters with Managed Identity enabled.

After working with identityProfile.kubeletidentity block, I'd propose that identityProfile.kubeletidentity.objectId should be exported instead of .clientId as it makes subsequent role assignment easier and avoids an additional Azure AD lookup.

Furthermore the export should also happen on the AKS Data Source.

hi @tezzigator

Thanks for opening this issue :)

Taking a look through this appears to be a duplicate of #6217 - rather than having multiple issues open tracking the same thing I'm going to close this issue in favour of that one; would you mind subscribing to #6217 for updates?

Thanks!

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!

Was this page helpful?
0 / 5 - 0 ratings