oomkilled

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 CPU limits make your apps (very) slow and costly. CPU throttling analyzed, with proof.

Memory Consumer for Java Application (OOM Killed)

kubectl plugin that explains why a container or pod died or restarted, with evidence and confidence labels

Workload-agnostic Kubernetes OOM watchdog sidecar: rescues memory-bursty containers via in-place pod resize (pods/resize), borrows memory under host-safety guards and returns it when pressure clears.

OOCKilled is OOMKilled for CPU

A tool for watching OOMKilled events in Kubernetes clusters.

eBPF-powered Kubernetes OOM diagnostics: kernel-level process attribution and memory-trajectory post-mortems

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.

Why Java containers get OOMKilled with nothing in the log, reproduced in a minute: exit 137 vs a diagnosable OutOfMemoryError, and the measured truth about MinRAMPercentage

Read-only Kubernetes pod triage — crash/OOM/saturation root-cause as a token-thrifty markdown digest. CLI + MCP server.