Open gorge511 opened 1 year ago
Note: We've had a lot of issues with GKE taints over time- we really need to rethink our model for them. See https://github.com/hashicorp/terraform-provider-google/issues/7928 for a related issue.
Can be closed, it's fixed, see https://github.com/hashicorp/terraform-provider-google/issues/7928 for details.
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
Google Terraform Provider 4.55.0
Affected Resource(s)
Expected Behavior
Node pool should be modified in place. This change works in the GCP Console WebUI. So there should be possibility to update taints without node pool recreation.
Also this works with
gcloud
. See the docs for update command.Actual Behavior
When you change the
taint
innode_config
block on the node pool the resource is forced to be recreated.There is a limitation written in the docs, but I think this is no longer relevant for non-default node pools.
See the forcing code in google provider. And see the
gcloud
command docs where you can see that--node-taints
is available in update operation.Steps to Reproduce
google_container_node_pool
withouttaint
in thenode_config
block.taint
in thenode_config
block.References