A high container restart count indicates the container has restarted more than a threshold (e.g. 5 times), often due to repeated crashes or failing liveness probes. Root cause should be fixed to avoid availability impact and extra node load.
Warning
N/A
- Report shows: Container <name> in pod <ns>/<pod> has <n> restarts
kubectl get podshows a high RESTARTS value
- Check pod events and container status:
kubectl describe pod <ns>/<name> - Check current and previous container logs:
kubectl logs <ns>/<name> -c <container>and--previous - Investigate OOM, overly strict startup/liveness probes, unavailable dependencies, or application bugs
- Adjust resource limits, probe parameters, or application logic and redeploy