important-leather-28796
12/23/2019, 5:26 PMlocation: us-central1-f
to create the cluster I get complaints about Cannot determine region: set in this resource, or set provider-level 'region' or 'zone'
. It is true, I intend to explicitly set project, zone, region. What do I need to pass to gcp.container.Cluster
to satisfy it for a zonal cluster?gentle-diamond-70147
12/23/2019, 6:03 PMimportant-leather-28796
12/23/2019, 6:07 PMgcp:region: us-central1
gcp:zone: us-central1-f
is allowing it to proceed. I really don’t want this because we are explicit with these settings and they are propagated from our identity
stackgentle-diamond-70147
12/23/2019, 7:00 PMgcp:zone
and gcp:region
) and set zone: "us-central1-a"
on my cluster and that worked for me. Is that what you want?important-leather-28796
12/23/2019, 7:01 PMlocation
for ClusterArgs
, where did you set zone
?gentle-diamond-70147
12/23/2019, 7:01 PMexport const k8sCluster = new gcp.container.Cluster("gke-cluster", {
initialNodeCount: nodeCount,
nodeVersion: masterVersion,
minMasterVersion: masterVersion,
zone: "us-central1-a",
masterAuth: { username, password },
nodeConfig: {
machineType: nodeMachineType,
oauthScopes: [
"<https://www.googleapis.com/auth/compute>",
"<https://www.googleapis.com/auth/devstorage.read_only>",
"<https://www.googleapis.com/auth/logging.write>",
"<https://www.googleapis.com/auth/monitoring>",
],
},
});
important-leather-28796
12/23/2019, 7:01 PMlocation
docs state that it accepts region or zonegentle-diamond-70147
12/23/2019, 7:01 PMzone
is deprecated.important-leather-28796
12/23/2019, 7:02 PMzone
at all in my current .d.ts
gentle-diamond-70147
12/23/2019, 7:07 PMup
finishes.location
works me in the same way.important-leather-28796
12/23/2019, 7:26 PMgcp:region
and gcp:zone
set to invalid
? or unset?gentle-diamond-70147
12/23/2019, 7:33 PMimportant-leather-28796
12/23/2019, 7:52 PM