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

:wave: hello!
I have a question about auth.

I have a Pulumi project which creates a bunch of resources in GCP using a service account. Among those, it creates a kubernetes cluster.
Then, I want to create k8s resources, but I’m getting a lot of permission errors because pulumi is trying to use the user configured under `gcloud` in the current machine (which makes sense, because I believe the kubeconfig for the clusters defers to the `gcloud` command for auth). Is there a way to explicitly tell pulumi to use the same service account it used for creating the GCP resources? I tried setting `GOOGLE_CREDENTIALS` but the behavior didn’t change.

Thanks