No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Trying to create a zonal gcp cluster, my setup is good for a regional but I want to create some smaller test clusters.  When I use `location: 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?

<https://gist.github.com/rosskevin/ac85c687f539912cdfdde15245ea5e22>

Setting:
```  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

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 use `location` for `ClusterArgs`, where did you set `zone`?

```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>",
        ],
    },
});```

`location` docs state that it accepts region or zone

I don’t see `zone` at all in my current `.d.ts`

Ah, I am on an old version. I'll upgrade after this `up` finishes.

Yea, `location` works me in the same way.

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?

It could be that you have other resources that are expecting a region or zone from the default provider.￼

I’m incrementally doing this one thing at a time, isolated to my cluster config