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

A transformation should work.

Also, if you're cluster is provisioned outside of the current stack, then setting the `kubernetes:kubeconfig` stack config would mean your k8s resources could use the "default" provider that comes with the stack.

<https://www.pulumi.com/docs/intro/cloud-providers/kubernetes/#configuration>

the main thing I’m enforcing is the namespace in my provider

but it looks like I can just configure `kubernetes:namespace` and not worry so much about it?

Yep, anything you configure on an explicit provider can be set via config on the default provider. 