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

do you mean if a deployment doesn't become healthy?

add `<http://pulumi.com/skipAwait|pulumi.com/skipAwait>: "true"` to the resources annotations

is that documented anywhere? And what does it do? I do want to wait, but not for as long.

<https://www.pulumi.com/blog/improving-kubernetes-management-with-pulumis-await-logic/>

you can also use `<http://pulumi.com/timeoutSeconds|pulumi.com/timeoutSeconds>`

I was about to post that :slightly_smiling_face:

I also added this to stackoverflow for other people to see: <https://stackoverflow.com/questions/64638116/change-pulumis-timeout-when-deploying-kubernetes-resources/64638117#64638117>

hm. I set it on the deployment and it is propagated down to the pod... but it still waits a long time before failing

```apiVersion: v1
kind: Pod
metadata:
  annotations:
    <http://linkerd.io/created-by|linkerd.io/created-by>: linkerd/proxy-injector stable-2.8.1
    <http://linkerd.io/identity-mode|linkerd.io/identity-mode>: default
    <http://linkerd.io/proxy-version|linkerd.io/proxy-version>: stable-2.8.1
    <http://pulumi.com/timeoutSeconds|pulumi.com/timeoutSeconds>: "60"
  creationTimestamp: "2020-11-01T23:45:50Z"```
I guess that is correct?

The `timeoutSeconds` annotation should still work, but you can have more fine-grained control using the `customTimeouts` options on any resource. (That option didn’t exist when the blog post Lee linked was written)

<https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/#CustomResourceOptions-customTimeouts>