kwatch runs inside your Kubernetes cluster, traces every failure to its root cause, and sends one message: what broke, why, who changed it and what to do next.
-
Updated
Nov 5, 2026 - Go
kwatch runs inside your Kubernetes cluster, traces every failure to its root cause, and sends one message: what broke, why, who changed it and what to do next.
Kubernetes operator that scales down workloads stuck in CrashLoopBackOff and similar terminal failure states
Captures the heap, threads and core of a Kubernetes container before it dies
Kubernetes operator that detects CrashLoopBackOff, alerts Slack with root cause, and auto-rolls-back bad deployments.
kubectl plugin that explains why a container or pod died or restarted, with evidence and confidence labels
Explains why a Kubernetes pod crashed: a kubectl plugin and in-cluster controller that turns crashes into 18 stable cause codes for Prometheus, Loki and Grafana.
This repo contains files related to k8s troubleshooting scenarios
Kubernetes lab demonstrating emptyDir storage behavior, blue-green deployment, service selector switching, and CrashLoopBackOff troubleshooting.
This repository simulates a one-time database migration/backup: Pod stuck on CrashLoopBackoff and no body cares.
Common Kubernetes troubleshooting scenarios and resolution steps.
Read-only Kubernetes pod triage — crash/OOM/saturation root-cause as a token-thrifty markdown digest. CLI + MCP server.
Troubleshooting Kubernetes CrashLoopBackOff with practical examples, root causes, kubectl debugging techniques, and fixes for container crashes, probes, and resource issues.
Rank pods by restart count with the last termination reason and exit code, turning a wall of CrashLoopBackOff into an ordered list of what to look at first.
CLI that summarizes CrashLoopBackOff pods across a cluster with their most recent logs.
To associate your repository with the crashloopbackoff topic, visit your repo's landing page and select "manage topics."