-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Update existing labels and taints of existing worker groups #1085
Comments
See https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/docs/faq.md#how-do-i-safely-remove-old-worker-groups and https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/docs/faq.md#why-are-nodes-not-recreated-when-the-launch_configurationlaunch_template-is-recreated for more info. |
Closing this. Feel free to re-open it the provided answer doesn't help you. |
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 have issues
Hey there,
i have an issue to update existing nodes with node labels and taints. The labels and taints are added to a node when add new worker group to our cluster but not if I am editing the
kubelet_extra_args
values of existing worker groups. Is this not possible or is this a bug?Here is the snippet of our terraform code:
Help appreciated. Best regards
Peter
I'm submitting a...
What is the current behavior?
If this is a bug, how to reproduce? Please include a code sample if relevant.
What's the expected behavior?
Are you able to fix this problem and submit a PR? Link here if you have already.
Environment details
Any other relevant info
We are using terraform cloud to keep our cluster state in sync and at best i want to changes to variable values directly applied to our cluster.
The text was updated successfully, but these errors were encountered: