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

So far it worked.
It did expose the problem with clashing URN. 

I was trying to adhere to the naming convention others used with plain yaml and as a result found that naming with metadata is where problems come into play for this.


I have to refactor to rely less on fixed naked which I prefer anyway, just gets more complex.

I think this extra complexity will solve helping prepare for blue green though, at least that's my guess.

Rather than have your Pulumi program reach out and deploy to all clusters, you could install the Pulumi Operator on each cluster and have it pull down a repo and deploy your stack that way. It's the more GitOps approach

Would it take the same exact Go Pulumi plan? How much of a shift is it from agent driven to operator? Not opposed to this but not certain about it yet. I'll reread docs soon on this more as I had looked on the past but it seemed a big shift from the approach I was taking.

Added follow-up related to unique URN's and using random here: <https://github.com/pulumi/pulumi-random>

Thanks!