This message was deleted.

you don’t need an apply, you just need to pass it.

oh, I see, we create the resources for the cluster within the ApplyT. I’ll give this a try out, thank you for the the reference to the example! should’ve checked there first 😅

I don’t think it’s necessary to wrap all of your resources in the ApplyT. There are some bugs that make it weird ( I think the provider exported is broken ), but you can construct your own from the kubeconfig:

// Save a kube provider for later use
	kubeconfig := awsCluster.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, &kubernetes.ProviderArgs{
		Kubeconfig: kubeconfig,
	})
	if err != nil {
		return err
	}

ah okay, i am not building out many of the kubernetes resources out through pulumi (yet), just a couple of the building blocks needed for our env. but this a good alternative to consider. the resource i’m wrapping in the apply is just an encrypted storageclass and didnt have any issues with it in the exported provider

Cool, yeah, that makes a lot of sense then. We’re adding a lot of things to the cluster in Pulumi, so it is much much nicer to be able to break out of the ApplyT