-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Better way to authenticate kubernetes provider to use this module #909
Comments
The token should be short-lived, so the exposure is somewhat limited. That being said, you should generally assume that Terraform state is sensitive and needs to be locked down. |
@morgante you're right, and I knew that, I was hoping for some alternatives to not storing it in the state 😃. At the very least, I think maybe the documentation can be improved with respect to:
Thoughts? I can send up PRs if needed. |
Yes, 1 hour. A PR to explain this more would be appreciated. |
@yashbhutwala just an idea but IIRC
|
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
The current recommended way to authenticate kubernetes provider in order to use this module is with "google_client_config" data resource. However, using this data resource means that the token generated by this resource is stored in Terraform state in plain text. I'm looking for recommendations or suggestions for alternative ways to authenticate the kubernetes provider that does not rely on storing sensitive auth information in TF state. Any ideas welcome, thanks!
Relevant Resources:
The text was updated successfully, but these errors were encountered: