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

1) By default, the Kubernetes provider will use your `$KUBECONFIG` environment variable or `~/.kube/config`. So I expect `127.0.0.1:32804` is likely coming from one of those. But if you're defining your GKE cluster in the same Pulumi project, you likely need to create an explicit `k8s.Provider()` as shown at <https://github.com/pulumi/examples/blob/master/gcp-ts-gke/cluster.ts#L42-L80> and then used for your Kubernetes resources as shown at <https://github.com/pulumi/examples/blob/master/gcp-ts-gke/index.ts#L19>.
2) The zone is configured for the GCP provider. One way to do this is with `pulumi config set gcp:zone us-central1-a`. More on this is at <https://www.pulumi.com/docs/intro/cloud-providers/gcp/setup/>.

1. You were right about #1.
2. Is it possible to configure the zone inside the script file instead of using `pulumi config set`?
3. I assume that `pulumi config set` updates a file that is stack-specific?

2. Yes, but you must create an explicit GCP provider to do this - see <https://www.pulumi.com/docs/intro/concepts/programming-model/#explicit-provider-configuration> and then <https://www.pulumi.com/docs/reference/pkg/gcp/provider/>.
3. Yes, that's correct - anything set with `pulumi config set` is stack-specific.