-
Notifications
You must be signed in to change notification settings - Fork 671
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
VPC IKS workers upgrade should be optional #1681
Comments
I agree, the automatic upgrade for the workers needs to be optional. There is no way we can run this on a production cluster, especially with stateful services that need some care when upgrading. Can we help add this functionality? We have experienced Go developers that would like to help. |
@mschenk42 yes you can gohead and contribute may be we need to introduce a bool argument |
Thanks, will do. Currently testing change. Will be submitting a PR soon. |
Fixed in latest release |
Fixed by #1694 |
When upgrading IKS version via terraform it also replaces all worker nodes in the cluster to upgrade them to the specified master version as well. This is a destructive behavior that brings your entire cluster down for an upgrade period.
Upgrading workers together with the master upgrade should be optional
https://github.com/IBM-Cloud/terraform-provider-ibm/blob/master/ibm/resource_ibm_container_vpc_cluster.go#L475
The text was updated successfully, but these errors were encountered: