kubernetes
Pod in CrashLoopBackOff state
CrashLoopBackOff
Fixes
- 1.Check pod logs: kubectl logs pod-name --previous
- 2.Verify the container entrypoint/command is correct
- 3.Check if liveness probe is failing and killing the container
- 4.Inspect resource limits — OOM may cause immediate restart
podcrashrestart
Related Errors
kubernetes4 fixes
Cannot pull container image
ImagePullBackOff|ErrImagePull
- •Verify the image name and tag exist in the registry
- •Check imagePullSecrets is configured for private registries
kubernetes4 fixes
Container killed due to out-of-memory
OOMKilled
- •Increase memory limits in the pod spec: resources.limits.memory
- •Profile the application to find memory leaks
kubernetes4 fixes
Pod stuck in Pending due to insufficient resources
Pending.*Insufficient (cpu|memory)|FailedScheduling.*Insufficient
- •Scale up the cluster or add nodes with more resources
- •Reduce resource requests in the pod spec