--- title: "#postmortem articles | Hashnode" description: "Explore 74 articles tagged #postmortem on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/postmortem" --- Tag # #postmortem 74 posts · 0 followers [KIM KYUNGHWAN](https://hashnode.com/@kkhdevs) · [6h ago](https://hashnode.com/posts/pods-stuck-pending-after-node-failure-why-didn-t-kubernetes-reschedule-them-to-the-other-node/6af68e354617070ad9bb638a) ### [Pods stuck Pending after node failure: why didn't Kubernetes reschedule them to the other node?](https://kkhdevs.hashnode.dev/pods-stuck-pending-after-node-failure-why-didn-t-kubernetes-reschedule-them-to-the-other-node?utm_source=hashnode&utm_medium=feed) Pods stuck Pending after node failure: a required NotIn node affinity and two topology spread defaults on a 2-node k3s cluster. How to check yours. 24 min read · [kkhdevs.hashnode.dev](https://kkhdevs.hashnode.dev/pods-stuck-pending-after-node-failure-why-didn-t-kubernetes-reschedule-them-to-the-other-node?utm_source=hashnode&utm_medium=feed) [KIM KYUNGHWAN](https://hashnode.com/@kkhdevs) · [15h ago](https://hashnode.com/posts/kubernetes-cronjob-pg-dump-backup-does-the-dump-end-up-on-the-same-node-as-the-database/6af619ce49efde299757baff) ### [Kubernetes CronJob pg\_dump backup: does the dump end up on the same node as the database?](https://kkhdevs.hashnode.dev/kubernetes-cronjob-pg-dump-backup-does-the-dump-end-up-on-the-same-node-as-the-database?utm_source=hashnode&utm_medium=feed) Kubernetes CronJob pg\_dump backup on k3s local-path: 5 of 7 dumps and every etcd snapshot were on the database's own disk. How to check yours. 21 min read · [kkhdevs.hashnode.dev](https://kkhdevs.hashnode.dev/kubernetes-cronjob-pg-dump-backup-does-the-dump-end-up-on-the-same-node-as-the-database?utm_source=hashnode&utm_medium=feed) [SelfHealing](https://hashnode.com/@selfhealing) · [4d ago](https://hashnode.com/posts/your-ai-agent-will-have-an-incident-here-s-the-15-minute-response-plan/6af185851085047c4da029df) ### [Your AI Agent Will Have an Incident. Here's the 15-Minute Response Plan](https://selfhealing.hashnode.dev/your-ai-agent-will-have-an-incident-here-s-the-15-minute-response-plan?utm_source=hashnode&utm_medium=feed) A no-code incident routine for founders and small teams: severity in two minutes, a containment ladder, customer corrections that don't make things worse, and postmortems that change controls instead of prompts. 8 min read · [selfhealing.hashnode.dev](https://selfhealing.hashnode.dev/your-ai-agent-will-have-an-incident-here-s-the-15-minute-response-plan?utm_source=hashnode&utm_medium=feed) [1](https://hashnode.com/posts/your-ai-agent-will-have-an-incident-here-s-the-15-minute-response-plan/6af185851085047c4da029df) [CGTRocketX](https://hashnode.com/@cgtrocketx) · [Oct 28](https://hashnode.com/posts/one-godot-4-racer-two-storefronts-what-broke-when-we-shipped-the-same-build-to-the-browser-and-google-play/6ae1cb3b773d7eaafe48b41a) ### [One Godot 4 racer, two storefronts: what broke when we shipped the same build to the browser and Google Play](https://cgtrocketx.hashnode.dev/one-godot-4-racer-two-storefronts-what-broke-when-we-shipped-the-same-build-to-the-browser-and-google-play?utm_source=hashnode&utm_medium=feed) CGT Rocket X Racer is a fan-made, landscape runner/racer built in Godot 4. It has one project and two release targets: a web build for desktop browsers and an Android build on Google Play. Play free i 8 min read · [cgtrocketx.hashnode.dev](https://cgtrocketx.hashnode.dev/one-godot-4-racer-two-storefronts-what-broke-when-we-shipped-the-same-build-to-the-browser-and-google-play?utm_source=hashnode&utm_medium=feed) [2](https://hashnode.com/posts/one-godot-4-racer-two-storefronts-what-broke-when-we-shipped-the-same-build-to-the-browser-and-google-play/6ae1cb3b773d7eaafe48b41a) [Parsa Mohammadi](https://hashnode.com/@tomosu) · [Sep 21](https://hashnode.com/posts/your-postmortem-template-was-written-for-humans-agents-break-it/6ab141b937263e2215e6465c) ### [Your postmortem template was written for humans. Agents break it.](https://tomosu.hashnode.dev/your-postmortem-template-was-written-for-humans-agents-break-it?utm_source=hashnode&utm_medium=feed) A free template built on the standard postmortem format, plus the fields you need when an AI coding agent, not a person, made the change. 2 min read · [tomosu.hashnode.dev](https://tomosu.hashnode.dev/your-postmortem-template-was-written-for-humans-agents-break-it?utm_source=hashnode&utm_medium=feed) [Human Business Works](https://hashnode.com/@humanbusinessworks) · [Aug 28](https://hashnode.com/posts/blameless-postmortem-government-contract-outage/6a91a279266bc596963c42d6) ### [Running a Blameless Postmortem When a Government Contract Is on the Line](https://humanbusinessworks.hashnode.dev/blameless-postmortem-government-contract-outage?utm_source=hashnode&utm_medium=feed) When an outage triggers a contractual incident report, blameless postmortems get harder. Here's how to satisfy a government client without turning the internal review into a blame exercise. 7 min read · [humanbusinessworks.hashnode.dev](https://humanbusinessworks.hashnode.dev/blameless-postmortem-government-contract-outage?utm_source=hashnode&utm_medium=feed) [Scott Boudreaux](https://hashnode.com/@scottcjn) · [Aug 24](https://hashnode.com/posts/node-monitor-perfectly-inverted/6a8c79315e8fca66f1caed0f) ### [Our Node Monitor Was Perfectly Inverted: Two Bugs That Cancelled Into a Wrong Answer](https://elyanlabs.hashnode.dev/node-monitor-perfectly-inverted?utm_source=hashnode&utm_medium=feed) A 200 is not evidence of a node, and we probed a path nothing serves. 6 min read · [elyanlabs.hashnode.dev](https://elyanlabs.hashnode.dev/node-monitor-perfectly-inverted?utm_source=hashnode&utm_medium=feed) [Scott Boudreaux](https://hashnode.com/@scottcjn) · [Aug 24](https://hashnode.com/posts/what-breaks-when-your-users-are-bots/6a8c79113984cc9752fe5b3a) ### [What Breaks When Your Users Are Bots](https://elyanlabs.hashnode.dev/what-breaks-when-your-users-are-bots?utm_source=hashnode&utm_medium=feed) 820 accounts that never once tripped a rate limit, and a review queue nobody ever opened. 7 min read · [elyanlabs.hashnode.dev](https://elyanlabs.hashnode.dev/what-breaks-when-your-users-are-bots?utm_source=hashnode&utm_medium=feed) [Kiwon Song](https://hashnode.com/@stockdigging) · [May 27](https://hashnode.com/posts/i-vibe-coded-a-stock-screener-into-production-then-my-2gb-server-oomed-and-google-de-indexed-me/6a166b57da253d50d410a027) ### [I Vibe-Coded a Stock Screener Into Production. Then My 2GB Server OOMed and Google De-Indexed Me.](https://stockdigging.hashnode.dev/i-vibe-coded-a-stock-screener-into-production-then-my-2gb-server-oomed-and-google-de-indexed-me?utm_source=hashnode&utm_medium=feed) Part 1 of "Vibe Coded, Real Consequences" — the OOM event that tanked my Search Console, every fix I shipped after, and what's still in flight. 15 min read · [stockdigging.hashnode.dev](https://stockdigging.hashnode.dev/i-vibe-coded-a-stock-screener-into-production-then-my-2gb-server-oomed-and-google-de-indexed-me?utm_source=hashnode&utm_medium=feed) [Daniel Posing](https://hashnode.com/@danposing) · [May 18](https://hashnode.com/posts/orchestrating-reliability-through-verification-proxies-unhappy-paths-2/6a0a90b93104e2aff00f67cf) ### [Orchestrating Reliability through Verification Proxies (Unhappy Paths #2)](https://danielposing.hashnode.dev/orchestrating-reliability-through-verification-proxies-unhappy-paths-2?utm_source=hashnode&utm_medium=feed) How a strict attribute limit turned a routine migration into a P0. Solving Read-Modify-Write race conditions with Python and verification proxies. 6 min read · [danielposing.hashnode.dev](https://danielposing.hashnode.dev/orchestrating-reliability-through-verification-proxies-unhappy-paths-2?utm_source=hashnode&utm_medium=feed) [1](https://hashnode.com/posts/orchestrating-reliability-through-verification-proxies-unhappy-paths-2/6a0a90b93104e2aff00f67cf)