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

To be clear - I know I can specify config options for the default k8s provider via `pulumi config set kubernetes:kubeconfig` but in my case I create a gke container and create kubeconfig that I want to use - is it possible to pass that kubeconfig to the default kubernetes provider instance or create my own instance of kubernetes provider and replace the default one?

Currently no - you can either use the existing ambient provider established via config settings, or must pass an explicitly created provider manually.

<https://github.com/pulumi/pulumi/issues/2059> is tracking offering a way to set the default provider.

Thanks - I had the same issue as described in the linked ticket…

<@UD81PU5JL> yeah this is something we’re actively working on. I deleted my kubeconfig file so I never use the ambient provider by accident — I always boot a GKE/EKS/AKS cluster and then deploy an app on it with the first-class providers.

Yes, I just can’t wait to get this feature released :smile: