Identify why a container repeatedly starts and exits without hiding the cause with manual restarts.
Before you start
Work on a copy or a controlled test when the change can affect production. Keep timestamps, screenshots and the previous configuration so the result can be compared.
Step by step
- Inspect Pod state, restart count, and recent events.
- Read current container logs and previous-instance logs.
- Check command, args, environment variables, secrets, volumes, and network dependencies.
- Review liveness/startup probes and memory/CPU limits.
- Fix the cause in the Deployment or chart and observe a new rollout.
Validation
Repeat the original test after the change and confirm that the expected service works without creating a new regression. Document the final state.