-
Notifications
You must be signed in to change notification settings - Fork 1.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
Upgrading to v21.0.0 forces recreation of node pools #1268
Comments
Hi, I have the same issue but caused by Having node pool without This happens while upgrading from
I am not sure if I can somehow override this or what the proper fix is here. |
Hi, it seems that there is no other way how to avoid node pool recreation than updating the state file manually. That's why @Flektoma and I developed this following jq -a '(.resources[] | select((.module // "" | endswith("module.gke.module.gke")) and (.type == "random_id")) | .instances[].attributes.keepers) |= (. + {enable_gcfs: ""})' default.tfstate > default.tfstate.new Just please check the diff before uploading the state file back to your backend if all the changes are valid. |
@bharathkkb can you please suggest to which file I should put it? Basically where you, as a user, will try to look for such information? New file in |
TL;DR
enable_gcfs
being added to state forces terraform to rebuild node poolsExpected behavior
Updating version of module should not rebuild node pools
Observed behavior
Terraform needs to rebuild the node pools
Terraform Configuration
Terraform Version
Additional information
No response
The text was updated successfully, but these errors were encountered: