This message was deleted.

If you want to create a

kubernetes provider

programmatically, you can just work with the output because a provider is also a

CustomResource

and does the await for you. The same applies for stack outputs you export. Just export the Output<string> and you will get the string. If you need programmatic access to the string value, this cannot be done synchronously, therefore just use the

apply

method like here: https://www.pulumi.com/docs/intro/concepts/programming-model/#apply

Thanks, although I've tried with apply already but you still end up with an Output<string>. Can I somehow programmatically save that gke kubeconfig into an actual string variable. There is a long winded explanation why I need this.

@billions-lock-80282 are you trying to get at the string prior to the plan finishing?

yes

Yeah, that's the hard part. There is no string there, because Outputs aren't fulfilled until the plan runs. It's like asking for an RDS address before the RDS instance is even created.

ah ok, the main issue is is that I have a separate cert-manager class that both eks and gke both call. But its using the

const kubeconfig = new KubeConfig();
            kubeconfig.loadFromString(JSON.stringify(kc));

IIUC that would need to become something like

kc.apply((kcString) => { 
    kubeconfig.loadFromString(kcString)
})

ok, I'll give that a try, thanks

I would assume that in the EKS case you are also working with an unresolved kubeconfig. Is there no way of just modifying the kubeconfig in flight (using apply) and handing it in the same way? Could you show the EKS way and your KubeConfig class to better understand what you are trying to do? I don’t see why you should require the resolved string…

I get the following error for gke kubeconfig

TypeError: unknown version: undefined