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

I solved it like so:
```command = new remote.Command(...) // generate kubeconfig to stdout
export const kubeconfig = kubeconfigs.admins.stdout;

const provider = new k8s.Provider("k8s", { kubeconfig });

new k8s.helm.v3.Release("foo", {...}, { provider });```
However, due to <https://github.com/pulumi/pulumi-command/issues/94|this bug>, it means I cannot refresh my stack :confused:

Thanks <@U03KC9FGRC5>. Have you tried using `remote.run` instead of `remote.Command`? As I understand it the only difference is that Command is managed and run will just execute, i.e. it won't actually be part of the stack.

Screenshot 2022-07-12 at 11.57.46.png

as far as I can tell, `run` is only available for local commands?

aha, that sucks. Well, in my case it doesn't matter since I'm running it locally, so I'll try run first.

can't you run yours locally though? gcloud should be able to reach the gcp api from your local machine too?

I’m not using gcloud, my `Command` is using `kubeadm` to generate the config for an on-prem cluster.

The k8s part should be the same once you have the kubeconfig, so it should still work for you though. Your command just needs to output the kubeconfig to stdout.

aha, of course, I just assumed you were using some cloud service. my bad

yea, now I have to figure out how to make the  gcloud command output to stdout, which seems surprisingly difficult.