Kubernetes operator that detects CrashLoopBackOff, alerts Slack with root cause, and auto-rolls-back bad deployments.
This repo contains files related to k8s troubleshooting scenarios
Kubernetes lab demonstrating emptyDir storage behavior, blue-green deployment, service selector switching, and CrashLoopBackOff troubleshooting.
Common Kubernetes troubleshooting scenarios and resolution steps.
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.
Troubleshooting Kubernetes CrashLoopBackOff with practical examples, root causes, kubectl debugging techniques, and fixes for container crashes, probes, and resource issues.
Explains why your Kubernetes pods crash — straight from live cluster state, no copy-pasting logs. Classifies failures into 17 stable cause codes (oom_killed, probe_liveness_failure, image_pull_auth...) as a kubectl plugin or an in-cluster controller exporting crash causes to Prometheus, Loki and Grafana. Optional BYO-key AI summaries.
Read-only Kubernetes pod triage — crash/OOM/saturation root-cause as a token-thrifty markdown digest. CLI + MCP server.
CLI that summarizes CrashLoopBackOff pods across a cluster with their most recent logs.
This repository simulates a one-time database migration/backup: Pod stuck on CrashLoopBackoff and no body cares.
To associate your repository with the crashloopbackoff topic, visit your repo's landing page and select "manage topics."