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 just hit something similar in Go, where I had to essentially get the kubeconfig out of the cluster as a string using an Apply

I think this issue helped me a bit - <https://github.com/pulumi/pulumi-eks/issues/602>

In Go, this ended up looking like:

```// Save a kube provider for later use
	kubeconfig := cluster.Kubeconfig.ApplyT(func(k interface{}) (string, error) {
		data, err := json.Marshal(k)
		if err != nil {
			return "", fmt.Errorf("kubeconfig is not a string")
		}
		return string(data), nil
	}).(pulumi.StringOutput)

	kubeProvider, err := kubernetes.NewProvider(ctx, awsCluster.Name, &amp;kubernetes.ProviderArgs{
		Kubeconfig: kubeconfig,
	})```

It looks like this is what I'm doing (although in TypeScript) but what I get is a kubeProvider that is somewhat 'poisoned', in that it appears to work, but if I create a resource with it, I get that odd error from inside Pulumi

It does seem like that linked issue might clear things up when it's fixed? Since I could use apply to turn the Output&lt;string&gt; of the kubeconfig into an Output&lt;KubernetesProvider&gt; and use that

Interesting.

That sounds right, but it also seems like that might be a long while (they link another blocking issue in there). It's a bit beyond my full understanding though

<@U03KSQ2GXQQ>: What kind of cluster are you creating? (EKS, GKS, AKS? Something else?) Not sure about the others, but if you’re dealing with EKS and use the `@pulumi/eks` package, you get a `provider` <https://www.pulumi.com/registry/packages/eks/api-docs/cluster/#provider_nodejs|output> you can use as a resource option for future K8S operations like:
```cluster = new eks.Cluster(...);

k8sThing = new k8s.core.v1...({args}, {provider: cluster.provider});```

It's kops, unfortunately, which doesn't seem to have an implementation out of the box. I'm making the cluster itself with a dynamic resource and then using an `.apply` on the output of that dynamic resource to look up the information to make a `kubeconfig`, which is how I'm getting the `Output&lt;string&gt;` that is the kubeconfig.

This all works great if the cluster is already up. I'm guessing because even though it's an `Output&lt;string&gt;`, it already has a valid value