You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a GKE Node Pool in a regional non-autopilot cluster, there's an option to list which zones the node will be created in. For example in a us-central cluster, we can create a nodepool that's located only in us-central1-a and us-central1-b, by specifying the --node-locations parameter when using the command gcloud container node-pools create (gcloud docs).
But when creating with ansible google.cloud.gcp_container_node_pool, there's no such parameter to specify that (ansible docs). Instead it will create the nodepool located in 3 different arbitrary zones. (for example us-central1-a, us-central1-b, and us-central1-f.
ISSUE TYPE
Feature Idea
COMPONENT NAME
google.cloud.gcp_container_node_pool
ADDITIONAL INFORMATION
The text was updated successfully, but these errors were encountered:
SUMMARY
When creating a GKE Node Pool in a regional non-autopilot cluster, there's an option to list which zones the node will be created in. For example in a
us-central
cluster, we can create a nodepool that's located only inus-central1-a
andus-central1-b
, by specifying the--node-locations
parameter when using the commandgcloud container node-pools create
(gcloud docs).But when creating with ansible
google.cloud.gcp_container_node_pool
, there's no such parameter to specify that (ansible docs). Instead it will create the nodepool located in 3 different arbitrary zones. (for exampleus-central1-a
,us-central1-b
, andus-central1-f
.ISSUE TYPE
COMPONENT NAME
google.cloud.gcp_container_node_pool
ADDITIONAL INFORMATION
The text was updated successfully, but these errors were encountered: