-
-
Notifications
You must be signed in to change notification settings - Fork 4.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
Suggestion - use the kubernetes provider to remove dependency on kubectl and config #353
Comments
I have made a PR for this. I have tested and the wait until cluster endpoint is ready is not needed as the creation of the eks clusters waits for this automatically. |
This is the PR: #355 |
I added the wait because I had inconsistent results i.e. it worked sometimes but not others. If you're confident it works reliably without the wait then I see no problem with removing it. Thanks for picking this up and submitting the PR - I was planning to do it myself but easter weekend got in the way and you beat me to it! 👍 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This is done |
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. |
This is just a suggestion and not an issue but would it not make sense to use the official terraform kubernetes provider to provision things like the aws_auth configmap instead of relying on null_resources, kubectl and a local kubeconfig file?
I have done something like this in the past:
The text was updated successfully, but these errors were encountered: