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

Kubeconfig generation for google_container_cluster #3097

Closed
pke0108 opened this issue Feb 21, 2019 · 3 comments
Closed

Kubeconfig generation for google_container_cluster #3097

pke0108 opened this issue Feb 21, 2019 · 3 comments

Comments

@pke0108
Copy link

pke0108 commented Feb 21, 2019

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. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

I have been observed that Azure resource azurerm_kubernetes_cluster is generating Kubeconfig as kube_config_raw.

Would be great helpful to get the same mechanism with certificate keys for GKE google_container_cluster also.

New or Affected Resource(s)

  • google_XXXXX
    google_container_cluster

Potential Terraform Configuration

# Propose what you think the configuration to take advantage of this feature should look like.
# We may not use it verbatim, but it's helpful in understanding your intent.

References

  • #0000
@ghost ghost added the enhancement label Feb 21, 2019
@danawillow
Copy link
Contributor

Closing this due to #3097 (comment) claiming it can already be done, but please feel free to comment and reopen if I misunderstood.

@ghost
Copy link

ghost commented Jun 14, 2019

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 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Jun 14, 2019
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