cuddly-leather-18640
06/17/2021, 3:38 PM{"Namespace":"default","Signal":"terminated","TaskQueue":"main-task-queue","WorkerID":"34276@Paymahns-Air@","level":"error","msg":"Worker has been stopped.","time":"2021-06-17T10:33:39-05:00"}
(notice the Signal
field) when it receives a SIGTERM or SIGINT. I’ve noticed that when I perform pulumi up
(with a new docker image) the pod gets killed without ever emitting the above log message which suggests to me that the pod is getting a SIGKILL without having the option to shutdown gracefully.
Is this how pulumi up
is intended to behave? Do I have something misconfigured? Is there another explanation?billowy-army-68599
06/17/2021, 6:07 PMcuddly-leather-18640
06/17/2021, 7:34 PMbillowy-army-68599
06/17/2021, 8:08 PMcuddly-leather-18640
06/18/2021, 3:25 PM