Kubernartes one pod is crashing repeatedly, any solution?

Question

I deployed an app using Kubernetes, but one pod is crashing repeatedly. How do I diagnose and fix it?

Sarthak Varshney · Answer

If a pod is crashing again and again in Kubernetes, here’s how you can find out what’s wrong and fix it: 1. Check the status of the pod Run this command: kubectl get pods Look at the STATUS column. If it says CrashLoopBackOff, it means the pod is starting, crashing, and then restarting again. 2. See the logs of the crashing pod Run: kubectl logs This shows what’s happening inside the pod before it crashes. For example, maybe the app can't connect to a database, or there's a code error. 3. Describe the pod for more details Run: kubectl describe pod This shows if there are issues like missing config maps, secrets, failed liveness probes, etc. 4. Check if there’s a problem in your app Common reasons for crashes: Wrong environment variables Missing files or configs Database not reachable Bug in your code Fix the issue in your code or deployment, and then re-deploy. 5. Temporary: Stop the pod from restarting If you want to debug the container manually, you can stop it from restarting: Change your deployment YAML and add this to the container: restartPolicy: Never Then apply it and debug the pod without it restarting again and again. 6. Check container exit code Run: kubectl get pod -o jsonpath='{.status.containerStatuses[0].state.terminated.exitCode}' This gives you the exit code. For example, 1 usually means there was an error in the app.

Kubernartes one pod is crashing repeatedly, any solution?

Answers (1)