OneLinersCommand workbench
Verified diagnostic signature

A Pod container repeatedly fails, is killed, or fails a health probe.

Match output from kubernetes, understand the likely cause, then continue with sourced, read-only checks.

Confidence
high
Platforms
linux · macos · windows
Verified
2026-07-24
Recognized output

Signature matched locally

OOMKilled

OneLiners matches this pattern in your browser. Your pasted output is not stored or indexed.

Likely causes

What usually produces this signal

  1. Application startup failure
  2. Memory limit
  3. Probe mismatch
  4. Missing dependency or configuration
Safe next checks

Collect evidence before changing the system

01

Rank Kubernetes pods by total container restart count

kubectl get pods -A -o json | jq -r '.items[] | [.metadata.namespace,.metadata.name,([.status.containerStatuses[]?.restartCount] | add // 0)] | @tsv' | sort -k3,3nr | head -<count>

The output matches the expected target and exits without an error.

02

Show recent Kubernetes warning events in chronological order

kubectl get events -A --field-selector type=Warning --sort-by=.lastTimestamp -o custom-columns='TIME:.lastTimestamp,NAMESPACE:.metadata.namespace,REASON:.reason,OBJECT:.involvedObject.name,MESSAGE:.message'

The output matches the expected target and exits without an error.

03

Rank Kubernetes pods by memory consumption

kubectl top pods -A --no-headers | sort -k4 -hr | head -<count>

The output matches the expected target and exits without an error.