Pod Keeps Restarting (CrashLoopBackOff)

A pod in CrashLoopBackOff is starting, failing, and being restarted over and
over. This article explains the usual causes and how to fix them. Most likely
first:

• The application fails to start — a missing environment variable or bad
  configuration.
• The liveness probe is failing before the application has finished starting up.
  Adding or lengthening a startup probe is the fix.
• The pod is exceeding its memory limit — see
  Pod Killed with OOMKilled.

Check the Logs tab first. If you have namespace access and need more detail:

# Logs from the container that crashed
kubectl logs <pod-name> -n <your-namespace> --previous

# Events showing the exit reason
kubectl describe pod <pod-name> -n <your-namespace>

Fix the cause in your Component's configuration and click Save.

Still having issues?

Raise a request with the namespace, the Component name, the pod status, and what
you have already tried.

Related articles

• Workload Resources and Health Checks — resource requests, limits and health checks
• Pod Killed with OOMKilled — the pod exceeded its memory limit
• Pod Stuck in Pending (FailedScheduling) — the pod never starts at all
• Pod Restarted During Node Maintenance — a restart with no change on your side
• Restart an Application or a Single Pod — restart without changing configuration
• Troubleshooting Common Issues — find your symptom
• Secret Not Found or Not Reaching Your Application — a missing secret or empty variable