A health-clinic portal ENTRYPOINT uses a shell wrapper that never f…

Question

A health-clinic portal ENTRYPOINT uses a shell wrapper that never forwards SIGTERM, so Pods hang until they are force-killed. What image design fix helps Kubernetes stop the container cleanly?

Accepted Answer

Run the application with an exec-form ENTRYPOINT/CMD so PID 1 receives SIGTERM directly — If a shell sits in front of your app like a receptionist who pockets the mail, Kubernetes' polite "please shut down" (SIGTERM) never reaches the real process. Use exec-form ENTRYPOINT/CMD so the app is PID 1 and hears the signal.

Answer

Set terminationGracePeriodSeconds to 0 on every Pod so signals become unnecessary

Answer

Replace SIGTERM handling with a liveness probe that kills the process every 30 seconds

Answer

Switch the workload from a Deployment to a completed Job so shutdown signals are ignored

A health-clinic portal ENTRYPOINT uses a shell wrapper that never forwards SIGTERM, so Pods hang until they are force-killed. What image design fix helps Kubernetes stop the container cleanly?

Short Explanation

Full Explanation