IKS cluster resources to handle Kube version update. #1989
Merged
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.
This PR addresses the following issues for the moment:
In this PR, both
ibm_container_cluster
andibm_container_vpc_cluster
resources updates the kube versions of worker node by setting theupdate_all_workers
field to true.To handle the wait time for worker node updation, new param
wait_for_worker_update
is introduced. If the cluster has more number of nodes and user not intended to wait till all the the nodes updated,wait_for_worker_update
can be set to false.We are working on new resource design to handle the IKS cluster update where the resource would be able to handle major, minor and patch updates.