This message was deleted.
# google-cloud
s
This message was deleted.
g
What's your full code look like?
Setting:
Copy code
gcp: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
stack
g
I removed all config values (
gcp:zone
and
gcp:region
) and set
zone: "us-central1-a"
on my cluster and that worked for me. Is that what you want?
i
I use
location
for
ClusterArgs
, where did you set
zone
?
g
Copy code
export 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>",
        ],
    },
});
i
location
docs state that it accepts region or zone
g
Oh I see that
zone
is deprecated.
i
I don’t see
zone
at all in my current
.d.ts
g
Ah, I am on an old version. I'll upgrade after this
up
finishes.
👍 1
Yea,
location
works me in the same way.
i
I’m not sure why 1-f would be different than 1-a, and I don’t spot anything else that would cause it
do you have
gcp:region
and
gcp:zone
set to
invalid
? or unset?
g
Unset.
It could be that you have other resources that are expecting a region or zone from the default provider.
i
I’m incrementally doing this one thing at a time, isolated to my cluster config