docs: add example for node draining #937
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR o'clock
Description
Im not sure if this fits into the repo. I did some research on the topic and want to share a possible solution. Im not sad if you reject this but still happy about any feedback.
There is an existing issue for that topic here #462
If you run a production cluster with this module an important feature is missing.
How to update eks worker kubernetes version or worker group variables without downtime?
One way to solve this is to create a lifecycle hook which will drain the node before shutting down instances.
Checklist