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

it's not like it doesn't get applied if it doesn't get ready, it's already in the k8s state, so it's somewhat pointless to wait for it to become ready before updating pulumi's state

this is, more or less, the reason I don’t manage K8s in Pulumi.  The objects under management are so dynamic, and need to be updated so frequently, and if/when (when) state gets out of whack, you’re kind of stuck fighting Pulumi before you can progress your deployment

out of curiosity, what do you use for managing kubernetes?

the workaround I've started using is to use the `<http://pulumi.com/skipAwait|pulumi.com/skipAwait>: "true"` on resources that have a tendency to fail like this