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

```  kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> (ingress-nginx):
    error: could not get server version from Kubernetes: Get "https://&lt;redacted ip&gt;/version?timeout=32s": dial tcp &lt;redacted ip&gt;:443: i/o timeout```
anyone know why the helm release resource seems to be making the above api call despite the cluster itself not being up yet?  The cluster resource is currently in `depends_on`

How did you construct the Kubernetes provider being used by the Helm resource? I’d think `depends_on` would handle it, but if you aren’t using an explicit provider you might need to do that.

annoyingly i can't find a good example programmatically generating the provider for GKE

Which language? The `kubernetes-gcp-{lang}` templates in <https://github.com/pulumi/templates> should have an example of generating a Kubeconfig for GKE.

Here’s the relevant lines from the Go template: <https://github.com/pulumi/templates/blob/master/kubernetes-gcp-go/main.go#L119-L142>

oh i think this is exactly what i was looking for.  I'm using python for devops, but we use go for prod code.  ty!