This message was deleted.
# kubernetes
s
This message was deleted.
b
do you mean if a deployment doesn't become healthy?
w
yes
b
add
pulumi.com/skipAwait: "true"
to the resources annotations
w
is that documented anywhere? And what does it do? I do want to wait, but not for as long.
you can also use
pulumi.com/timeoutSeconds
w
I was about to post that 🙂
thanks
b
w
hm. I set it on the deployment and it is propagated down to the pod... but it still waits a long time before failing
Copy code
apiVersion: v1
kind: Pod
metadata:
  annotations:
    linkerd.io/created-by: linkerd/proxy-injector stable-2.8.1
    linkerd.io/identity-mode: default
    linkerd.io/proxy-version: stable-2.8.1
    pulumi.com/timeoutSeconds: "60"
  creationTimestamp: "2020-11-01T23:45:50Z"
I guess that is correct?
b
try setting it on the service
w
ok, thanks
g
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
b
ooh TIL, thanks @gorgeous-egg-16927