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

i wouldn't think it's possible to ignore changes to a resource's provider because the provider determines where the resource itself is created. wanting to ignore it may be a yellow/red flag in your program. imagine if the provider was changed to a different K8s cluster and then ignored by some resources. It would be an absolute nightmare to debug that type of situation!

Yeah it's not ideal but people kept just making new providers where they needed them instead of passing them around, so they ended up pointing to the same thing. Aliases and such can fix, but just ignoring provider changes would have been more straight forward in some ways.