Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Deployment Credentials for AKS #934

Closed
tombuildsstuff opened this issue Mar 5, 2018 · 5 comments
Closed

Feature Request: Deployment Credentials for AKS #934

tombuildsstuff opened this issue Mar 5, 2018 · 5 comments

Comments

@tombuildsstuff
Copy link
Contributor

tombuildsstuff commented Mar 5, 2018

Chatting internally about using the azurerm_kubernetes_cluster resource - we should look into returning the Kubernetes credentials, which are needed to connect to the cluster and could be used in other resources/provisioners.

We return this information in the equivalent resource in Google Cloud - and it appears to be available in the Azure CLI too although it is via connecting to the box and using secure copy.

@paultyng
Copy link
Contributor

paultyng commented Mar 7, 2018

Here is an example workaround for ACS in the TF guides repo: https://github.com/hashicorp/terraform-guides/blob/master/infrastructure-as-code/k8s-cluster-acs/main.tf#L74

@paultyng paultyng assigned paultyng and unassigned paultyng Mar 7, 2018
@paultyng
Copy link
Contributor

paultyng commented Mar 7, 2018

I think the other issue with this is the resource currently only gets the public SSH key data, not the private key, so we'd have to add that in order to connect to the machine I think? Perhaps this should just be like a separate data source to pull these credentials?

@rberlind
Copy link

I would love it if the new azurerm_kubernetes_cluster did return the credentials (3 keys/certs) the way the GKE equivalent does. The code you referred to to work around is by me. :)

@tombuildsstuff
Copy link
Contributor Author

Support for this shipped in v1.5.0 and can be found in the kube_config block - as such I'm going to close this issue.

@tombuildsstuff tombuildsstuff modified the milestones: Future, 1.5.0 May 22, 2018
@ghost
Copy link

ghost commented Mar 31, 2020

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!

@ghost ghost locked and limited conversation to collaborators Mar 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants