rough-author-69114
07/12/2022, 8:50 AMpulumi_gcp.container.Cluster
and then want to deploy Strimzi operator with pulumi_kubernetes.helm.v3.Chart
. The problem I run into is that I don't personally have access to the cluster until I run gcloud container clusters get-gredentials <cluster_name> --region <region>
and generate the configuration, with certificates, for the cluster. I have a few ideas but I feel like I'm missing something that should work better.
Idea 1:
I can run the command to get the credentials from gcloud with pulumi_command.local.Command
after the creation of the cluster and before the Chart.
I don't particularly like this idea because it changes the state of my personal environment. For the time being it is not a problem, but once we start working with multiple clusters and multiple developers it is bound to cause problems.
And then I'm out of ideas. I'll start by trying idea 1 but I hope I can get some more information here.dazzling-oxygen-84405
07/12/2022, 10:33 AMcommand = 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 šrough-author-69114
07/12/2022, 10:57 AMremote.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.dazzling-oxygen-84405
07/12/2022, 10:58 AMrun
is only available for local commands?rough-author-69114
07/12/2022, 11:01 AMdazzling-oxygen-84405
07/12/2022, 11:02 AMCommand
is using kubeadm
to generate the config for an on-prem cluster.rough-author-69114
07/12/2022, 11:08 AM