google_container_node_pool should be able to create additional node pools

[hashibot]

This issue was originally opened by @devth as hashicorp/terraform#15002. It was migrated here as part of the provider split. The original body of the issue is below.

---

Expected Behavior

google_container_node_pool should be able to create node pools in zones other than the zone that the original cluster was created in.

Actual Behavior

Attempting to create a google_container_node_pool in a zone other than the zone the original cluster was created in results in an error like:

google_container_node_pool.prod-us-central1-b-m: Error creating NodePool: googleapi: Error 404: The resource "projects/myapp-prod-m/zones/us-central1-b/clusters/us-central1-prod-m" was not found., notFound

[danawillow]

Hey @devth, I don't think this is possible in google cloud at all. If you take a look at the cloud console, you don't get an option for what zone to create the cluster in. In gcloud the zone argument says:

The compute zone (e.g. us-central1-a) for the cluster

which makes me think it has to be the same.

Let me know if you find evidence to the contrary and I'll see what I can do, but closing this for now.

[devth]

@danawillow you're right!

There is a different mechanism for adding/removing zones on a cluster, e.g.:

gcloud beta container clusters update $cluster_name \
  --additional-zones us-central1-b

Could Terraform use this when updating the cluster itself?

[danawillow]

Is that the same as #104? If so, support has been checked in and will be available in the next release.

[devth]

Oops, yeah it is. I missed that. Thanks!!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!