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

the way to handle this is to set a provider resource on your Kubernetes resources:
<https://www.pulumi.com/docs/reference/pkg/kubernetes/provider/>

you can specify a specific context for each <https://www.pulumi.com/docs/reference/pkg/kubernetes/provider/#context_nodejs>

Didn’t know there was an ambient context for kubernetes

Although, I like that approach because I can just swap providers out from rendering to yaml to deploying

Kinda in this vein, is there a way to disable persistence of config? I’d like to force certain values to be provided at the CLI every time