Change of flavor causes recreation of ibm_container_vpc_cluster

[GrbrELO]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Question

Hi guys, I have the following question, is it intentional that changing the flavor (default workerpool) of the ibm_container_vpc_cluster resource triggers a replacement/recreation of that cluster. That said, I am aware of the documentation which states "Forces new resource" for that particular argument but that is the same for the worker_count or zones (name & subnet_id) arguments, which both can be changed (increased/decreased) without causing a cluster recreation.

That makes me wonder, is that intended and if, why?

New or Affected Resource(s) or Datasource(s)

• ibm_container_vpc_cluster

References

I am aware that #2949 or #4159 are sort of related, because if that default worker-pool would not be bound to the cluster, that behavior would not be a problem. But since this is the way it is, we have to get on with it. However, in my opinion it would be easier to deal with it, when changing the flavor of the default worker would not result in a destroyed and recreated cluster.