-
-
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
Kubernetes upgrade of worker_groups and worker_groups_launch_template #986
Comments
I believe this will work:
|
The module, by default, will not recreate the worker nodes when modifying any of their attributes, like cluster version. Kubernetes is a complicated beast and does not take well to all the nodes being deleted at once. This will likely cause interruptions to your workloads. Suggested processes for safely recreating the nodes can be found in the FAQ #937 contains an example of how to automate the draining of nodes. |
Thanks @dpiddockcmp , exactly what I was after! Coming from GKE thought the process would be handled automatically by AWS hence my confussion. |
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
I'm submitting a...
What is the current behavior?
I have only recently started using this module with worker_groups and worker_groups_launch_template but cannot find (apologies if I missed it somehow) procedure for Kubernetes upgrades. Setting
cluster_version
upgrades Kubernetes master but all nodes in my cluster remain on previous version.My cluster is created with the below block
If this is a bug, how to reproduce? Please include a code sample if relevant.
What's the expected behavior?
All nodes in the cluster are on the same version as the master
Are you able to fix this problem and submit a PR? Link here if you have already.
Environment details
Any other relevant info
The text was updated successfully, but these errors were encountered: