This message was deleted.

Here is the code

Pulumi waits for services to become ready, and it sounds like one of your services never initialized correctly. You likely want to look at the status of the pods targeted by the selector mentioned in the error message to see why those pods aren’t starting up correctly (they may be crash-looping, or there may not be nodes available for them to run on). If you want to allow them to fail, but still have the Pulumi deployment succeed, you can use skipAwait: https://www.pulumi.com/blog/improving-kubernetes-management-with-pulumis-await-logic/

The problem is that none of those pods targeted exist. I think Pulumi is incorrectly calculating resource graph for this chart. The services exist but the pods don't and thus Pulumi just waits endlessly. This happens for all of there services in the screenshot. I can try to add the skipAwait to each of these services