This message was deleted.
# kubernetes
s
This message was deleted.
d
I solved it like so:
Copy code
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 this bug, it means I cannot refresh my stack šŸ˜•
r
Thanks @dazzling-oxygen-84405. 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.
d
as far as I can tell,
run
is only available for local commands?
r
aha, that sucks. Well, in my case it doesn't matter since I'm running it locally, so I'll try run first.
šŸ‘ 1
can't you run yours locally though? gcloud should be able to reach the gcp api from your local machine too?
d
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.
r
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.