Operational Playbook/crashloop
CrashLoopBackOff Triage & Exit Code Analysis
Diagnose container exits, distinguish between Exit Code 137 (OOMKilled) and Exit Code 1 (Application Error), and execute safe remediation.
1. Inspect Pod Exit Code & Termination Reason
kubectl get pod <pod-name> -n <namespace> -o jsonpath='{.status.containerStatuses[*].lastState.terminated}'2. Fetch Previous Container Logs Before Crash
kubectl logs <pod-name> -n <namespace> --previous --tail=100
3. If Exit Code 137 (OOMKilled): Inspect Memory Requests vs Limits
kubectl top pod <pod-name> -n <namespace> --containers kubectl describe pod <pod-name> -n <namespace> | grep -A 4 'Limits:'
4. Autonomous Mitigation Policy Applied by AetherKube
# AetherKube autonomous-healing automatically raises limits up to 2x burst ceiling
kubectl patch deployment <deployment-name> -n <namespace> \
--type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/resources/limits/memory", "value": "512Mi"}]'