Skip to main content
DevOps Insightsguides & answers

Tag

#troubleshooting

2 articles found

#troubleshootingClear all
Diagram of Reading the memory curve: 1. Flat, near the limit, 2. Raise the limit, 3. Steady climb, regular kills, 4. Fix the code, 5. Fine, then one big request, 6. Size for the peak.
3 min
KubernetesIntermediateNew

OOMKilled and Exit Code 137: Limit, Leak or Spike?

OOMKilled means the kernel killed a Kubernetes container for using too much memory. How to tell a low limit from a leak or a one-off spike before you raise anything.

#Kubernetes#troubleshooting

Neeraj Jha

Diagram of One turn of the loop: 1. Container starts, 2. It exits, 3. Kubernetes restarts it, 4. Back-off grows, 5. You read the previous run.
3 min
KubernetesBeginnerNew

CrashLoopBackOff: Find the Cause in Three Commands

CrashLoopBackOff means a Kubernetes container keeps exiting and being restarted. Read the previous container's logs, its exit reason and the pod events, and the cause is usually on screen.

#Kubernetes#troubleshooting

Neeraj Jha