Quick troubleshooting view
The container repeatedly starts and exits while Kubernetes progressively increases the restart delay.
- Application startup failure
- Missing secret, variable, or volume
- Overly aggressive probe
- Use kubectl describe pod for events
- Use kubectl logs --previous for the prior crash
- Review probes and resource limits
- Correct only the component confirmed by the checks
- Retest the original symptom after the change
- Escalate with collected evidence when the cause remains unclear
Contextual technician plan
Perform this check and preserve the observed result before changing configuration.
“Use kubectl describe pod for events” should produce an observation that clearly confirms or rules out “Application startup failure”.
If the observation is normal, lower “Application startup failure” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “Application startup failure” first. Related action: Correct only the component confirmed by the checks.
Perform this check and preserve the observed result before changing configuration.
“Use kubectl logs --previous for the prior crash” should produce an observation that clearly confirms or rules out “Missing secret, variable, or volume”.
If the observation is normal, lower “Missing secret, variable, or volume” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “Missing secret, variable, or volume” first. Related action: Retest the original symptom after the change.
Perform this check and preserve the observed result before changing configuration.
“Review probes and resource limits” should produce an observation that clearly confirms or rules out “Overly aggressive probe”.
If the observation is normal, lower “Overly aggressive probe” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “Overly aggressive probe” first. Related action: Escalate with collected evidence when the cause remains unclear.
Repeat the same validation test after the correction and confirm the original symptom is gone. Validate stability before closing the incident.
Before changing configuration, record the current value and a way back.
Escalate with the exact symptom, scope, timestamp and completed checks when the issue remains unresolved.
＋Open the complete detailed guideDetailed explanations and original troubleshooting content.
The container repeatedly starts and exits while Kubernetes progressively increases the restart delay.
Likely causes
- Application startup failure
- Missing secret, variable, or volume
- Overly aggressive probe
- Memory limit exceeded
Checks in priority order
- Use kubectl describe pod for events
- Use kubectl logs –previous for the prior crash
- Review probes and resource limits
- Check the Deployment configuration
When to escalate
Escalate when the failure affects multiple users, a production dependency is unavailable, or logs show a component outside your control. Include timestamps, scope, tests already performed, and the last known working state.