# Pod Lifecycle - A POD deletion after a timeout, not immediately. Why?

**URL:** <https://discuss.kubernetes.io/t/pod-lifecycle-a-pod-deletion-after-a-timeout-not-immediately-why/27194>\
**Category:** General Discussions\
**Created:** [February 23, 2024, 9:06am UTC](https://discuss.kubernetes.io/t/pod-lifecycle-a-pod-deletion-after-a-timeout-not-immediately-why/27194 "2024-02-23T09:06:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Habu](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/habu/32/14357_2.png) [@Habu](https://discuss.kubernetes.io/u/Habu)\
**Post date:** [February 23, 2024, 9:06am UTC](https://discuss.kubernetes.io/t/pod-lifecycle-a-pod-deletion-after-a-timeout-not-immediately-why/27194/1 "2024-02-23T09:06:53Z")

</div>

Hi all,

My first post here and haven’t found an answer here yet, so I’m free and open to any bashings. 😉

Since the version 1.27.7 (but actually since some latest OS version coming with AKS), I’ve observed an issue, which I’ve described here: [[BUG] Pods Are Not Terminated If An AKS Node Is Stopped · Issue #4093 · Azure/AKS · GitHub](https://github.com/Azure/AKS/issues/4093)

As per [Pod Lifecycle | Kubernetes](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/): “If a Node dies, the Pods scheduled to that node are scheduled for deletion after a timeout period”

How long is this timeout? From the testing coming from the AKS issue 4093 it seems it’s around 5 minutes. Which means, that if a node dies, then a pod enters a Terminating (Unknown in fact) state after ~5 minutes, not immediately. If that’s the case, then why is this timeout so long?

Many thanks for any info in advance!

Best regards

Stefan