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

<@U01CPE961M2> this doesn't look correct, you're passing the provider as data into the secret? What are you trying to do?

I am not passing any data to the kubernetes Provider, I am relying on the default "read from ~/.kube/config". I would like to copy the kubeconfig content into a secret

you haven't actually read the file, all you've done is instantiated an empty provider. You need to use:
<https://www.pulumi.com/registry/packages/kubernetes/api-docs/provider/#kubeconfig_nodejs>

and read the filesystem file. The ambient provider doesn't read anything from disk

I'm sorta wondering why you want to put the kubeconfig in a secret though, you shouldn't really ever need to do that

I need the kubeconfig content for another application, nothing to do with Pulumi.

got it. it still shouldn't be needed, because anything running in cluster can just use service account authentication.

but ultimately, you'll need to read the file from disk.

Yes, fair comment about the service account, in this case it is just easier to provide the kubeconfig for the application I am using.
Anyway thanks for the suggestion.