-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
AWS Profile in kubeconfig template #39
Comments
Hi @mschuchard This sounds good but I think this is a duplicate request. We just started discussing a similar (if not the same) issue here a day ago. Let me know if your use case can be accommodated by implementing what's proposed there. |
I do not see any mention of implementing AWS profiles into the kubeconfig in that issue. Version 1.1.0 is currently failing for the customer because EKS cannot be reached due to the kubeconfig not using the correct AWs profile since that is not customizable in this module. Having separate kubeconfigs is fine, but in reality people are likely going to be merging their kubeconfigs and then differentiating between them via |
I submitted PR #49 which provides the ability to specify a generic map of environment variables to be appended to the kubeconfig. |
This is addressed having just merged #49 . Closing this up. |
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
I'm submitting a
For my current delivery, the customer has credentials with multiple profiles and not only needs to specify different profiles per cluster, but has no
default
profile.It would be great if the
kubeconfig.tpl
could be modified:where the default Terraform value to populate the template would be
default
to ensure no regression.I wanted to start a discussion before a PR to ensure best path forward on this. Thanks!
The text was updated successfully, but these errors were encountered: