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

cross-posting since it involves `k8s.yaml.ConfigFile`

I use different stacks for that, as I also haven't managed to find a solution

this problem really makes pulumi unusable for multi-cluster setups.
is there really not an easy solution around this?

it’s not feasible for me to use different stacks. we have way too many stacks already, and introducing another one here would have a multiplicative effect and make it unmanageable

i looks like i will have to introduce a manual step in our infra setup and sidestep pulumi for this case. i really really don’t want to do that though