Most people stare at logs too long. Kubernetes already tells you why your pod died.
Fastest diagnostic command:
kubectl describe pod <pod-name>
Look for:
Daily micro-tips for C#, SQL, performance, and scalable backend engineering.
Most people stare at logs too long. Kubernetes already tells you why your pod died.
Fastest diagnostic command:
kubectl describe pod <pod-name>
Look for:
Last State: Terminated Reason: OOMKilled
Why this matters:
Logs may be empty if the container never fully started.
Real fix:
Increase memory requests, not limits:
resources:
requests:
memory: "512Mi"
limits:
memory: "1Gi"
Result:
Stable pods, no restart loops, predictable scheduling.