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

Is there a way to disable this check? My pods can take a significant amount of time to startup
```kubernetes:apps/v1:Deployment api-deployment updating (0s) [diff: ~spec]; Waiting for app ReplicaSet to be available (0/1 Pods available)```

you can use the `<http://pulumi.com/skipAwait|pulumi.com/skipAwait>: true` annotation, or as of 4.18 you can use `<http://pulumi.com/waitFor|pulumi.com/waitFor>` to specify custom wait conditions

`skipAwait` has some buggy interactions with deletions so i’d definition recommend `waitFor`

Can you clarify how waitFor would be used here? I don't want it to wait at all, so adding a wait condition seems counter intuitive :sweat_smile:

for example if you annotate with `<http://pulumi.com/waitFor|pulumi.com/waitFor>: condition=Progressing` that won’t wait for it to become Available

Ahhh, I see! What if the update to the deployment doesnt cause a rollout?

good point :slightly_smiling_face: `condition=ReplicaFailure=False` might do what you need, you can also pick an arbitrary json path like `jsonpath={{spec.replicas}}` which will succeed immediately as long as the field is set, although that’s definitely more hacky