---
title: "Comment by indiainfranotes on \"Your pods aren't crashing - they're being interrupted mid-sentence\" | Hashnode"
description: "plot twist: install guides without a signed runtime tip stay trust-the-logo. 1 cut: when the outage dispute hits, can a buyer GET proof of what ran, or only ano"
url: "https://hashnode.com/posts/graceful-shutdown-sigterm-kubernetes-pod-termination/6aafc10765cac69d92cbd486/comment/6ab842f022837342f7a9d9f0"
---

[Discussion](https://hashnode.com/posts/graceful-shutdown-sigterm-kubernetes-pod-termination/6aafc10765cac69d92cbd486)

Comment [Your pods aren't crashing - they're being interrupted mid-sentence](https://hashnode.com/posts/graceful-shutdown-sigterm-kubernetes-pod-termination/6aafc10765cac69d92cbd486)

[indiainfranotes](https://hashnode.com/@indiainfranotes)

[Sep 26](https://hashnode.com/posts/graceful-shutdown-sigterm-kubernetes-pod-termination/6aafc10765cac69d92cbd486/comment/6ab842f022837342f7a9d9f0)

plot twist: install guides without a signed runtime tip stay trust-the-logo.

1 cut: when the outage dispute hits, can a buyer GET proof of what ran, or only another vendor badge?

local flags help. receipts settle arguments.

[JAY TANK](https://hashnode.com/@jaytank)

[Sep 28](https://hashnode.com/posts/graceful-shutdown-sigterm-kubernetes-pod-termination/6aafc10765cac69d92cbd486/comment/6ab842f022837342f7a9d9f0#reply-6ab9df741805e09f733edc32)

Thanks for following up - same fair point, this time framed around outage disputes rather than billing.

To keep scope clear: this article is about Kubernetes' own pod-termination mechanics (SIGTERM, the grace period, preStop hooks, and getting readiness to flip before the signal lands), not about producing evidence for a dispute between a buyer and an operator. For what it does cover, nothing is gated behind a "vendor badge" - kubectl describe pod, kubelet logs, and the pod's own terminationGracePeriodSeconds are the actual source of truth, and any operator can pull them directly rather than taking anyone's word for it.

The scenario you're describing - a buyer who doesn't control the cluster needing independently verifiable, signed proof of runtime behavior after an outage - is a real problem, but it's an attestation/provenance question, not a shutdown-mechanics one. It's outside what this post is trying to do. If that gap is what you're getting at, I'd be glad to dig into it as its own topic.
