Terraform-provider-azurerm: Feature Request: Export AKS clusterAdmin credentials

Created on 30 Nov 2018 · 2Comments · 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

Add clusteradmin exported attributes for azurerm_kubernetes_cluster.

Currently the Terraform AKS resource only exports the kube_config for clusterUser.

After creating an Azure AD enabled RBAC cluster, one must run "az aks get-credential --admin" in order get the clusterAdmin credentials to setup RBAC.

If azurerm_kubernetes_cluster exported clusterAdmin credentials then those attributes could be used as inputs to the Terraform kubernetes provider and the resource "kubernetes_cluster_role_binding" can be used to setup RBAC.

New or Affected Resource(s)

azurerm_kubernetes_cluster

Potential Terraform Configuration

output "kube_config_admin" {
  value = "${azurerm_kubernetes_cluster.k8s.kube_config_admin_raw}"
}

References

https://www.terraform.io/docs/providers/kubernetes/r/cluster_role_binding.html

enhancement servickubernetes-cluster

Source

haodeon

👍13

Most helpful comment

This is important especially when working with RBAC and AAD enabled on AKS and you want to provision clusterrolebindings for your users.

Current workaround is to integrate the following one into your TF deployment for AKS. Otherwise you don't have a chance after the AKS deployment process finish to do additional configuration tasks against the cluster itself.

resource "null_resource" "k8s" {

  provisioner "local-exec" {
    command = "az aks get-credentials --resource-group ${azurerm_resource_group.k8s.name} --name ${var.cluster_name} --admin"
  }
}

Since TF only support AKS without RBAC or AKS with RBAC & AAD and not the option AKS with RBAC currently. It is important to have this capability.

neumanndaniel on 5 Dec 2018

👍3

All 2 comments

This is important especially when working with RBAC and AAD enabled on AKS and you want to provision clusterrolebindings for your users.

resource "null_resource" "k8s" {

  provisioner "local-exec" {
    command = "az aks get-credentials --resource-group ${azurerm_resource_group.k8s.name} --name ${var.cluster_name} --admin"
  }
}

Since TF only support AKS without RBAC or AKS with RBAC & AAD and not the option AKS with RBAC currently. It is important to have this capability.

neumanndaniel on 5 Dec 2018

👍3

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!