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

Looking at this blog <https://www.pulumi.com/blog/kubernetes-yaml-generation/|https://www.pulumi.com/blog/kubernetes-yaml-generation/> you can render the pulumi resources to yaml.  I notice that for every object you need to provide it with the provider config.  Is there a way to make it more dry, such that you create a provider and tell pulumi to use it for all objects?

AFAIK you either use the default provider or you have to specify it every time

I was looking for a DRY solution too for AWS but couldn't find it for now

You can use runtime stack transformations for this: <https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/runtime/#registerStackTransformation>

See this recent blog post which has code examples in every language for automatically applying tags. You could try something similar for injecting a provider: <https://www.pulumi.com/blog/automatically-enforcing-aws-resource-tagging-policies/#automatically-applying-tags>

Thanks <@UQ8K13T7X> one last question.  I currently have 5 gke cluster that were provisioned by terraform.  Is a remote state reference through pulumi the best way to create a provider to each cluster or is there a better way?