
Kubernetes Exit Codes Explained: 0, 1, 126, 127, 137, 139, 143 and What Each Means
Complete reference to Kubernetes exit codes 0, 1, 126, 127, 137, 139, 143. What each means, the 128+N formula, and how to debug every one in production.
How is Sherlocks.ai different from k8sgpt or RunWhen? A field report comparing scope, production readiness, and what each tool actually does when an incident hits your Kubernetes cluster.

| Tool | Watches | Misses |
|---|---|---|
| Sherlocks.ai | Metrics, logs, traces, change events, tickets, cloud services, databases, queues and Kubernetes | |
| k8sgpt | Kubernetes objects & events | Everything outside the cluster |
| RunWhen | K8s manifests and upgrade state | App-level signals and multi-cloud context |
The short version: k8sgpt and RunWhen know a lot about what’s inside your cluster. Sherlocks looks at the whole system cloud services, queues, the noisy neighbour DB, you name it. You can check how Sherlocks compares to enterprise observability platforms like PagerDuty, New Relic, and Datadog.
Sherlocks.ai
k8sgpt
RunWhen
Sherlocks drops into your Slack or Zoom bridge, answers follow-ups, tracks action items and drafts the RCA before the smoke clears.
k8sgpt and RunWhen live in a CLI or their own dashboard you run them, read the output, and take it from there.
Sherlocks never sleeps. It scans telemetry around the clock and raises a flag before the pager barks.
k8sgpt and RunWhen kick in after you ask them to look or on a scheduled scan.
| Feature | Sherlocks.ai | k8sgpt | RunWhen |
|---|---|---|---|
| Datadog / CloudWatch / Grafana integration | ✔️ | ❌ | ❌ |
| Hybrid / on-prem deploy | ✔️ | ✔️ (binary) | ⭕ |
| SOC 2 roadmap | In progress | Community OSS | In progress |
| Human-in-loop approvals | ✔️ | N/A | Rule-based |
If that sounds useful, let’s chat. I’m always happy to walk through a live demo on your own stack.
Stay stable, ship faster. 🚀

Complete reference to Kubernetes exit codes 0, 1, 126, 127, 137, 139, 143. What each means, the 128+N formula, and how to debug every one in production.

What will AI SRE look like in the next 5 years? A grounded forecast on autonomy tiers, agent architecture, pricing shifts, and the next layer up.

A pod in CrashLoopBackOff is a pod that keeps crashing right after it starts, and Kubernetes is slowing down restart attempts. This guide covers what it means, the six real causes, how to diagnose with kubectl, and how to stop it coming back.