Interview Kubernetes, Docker, Helm & Podman

What is graceful termination, and how do preStop hooks and terminationGracePeriodSeconds work?

Kubernetes, Docker, Helm & Podman · Intermediate level

Answer

Graceful termination starts when Kubernetes sends SIGTERM to the container, optionally runs a preStop hook, waits for terminationGracePeriodSeconds, and then sends SIGKILL if the process has not exited.

Technical explanation

preStop runs before SIGTERM handling completes but counts inside the grace period, so long hooks can consume shutdown time.

Applications should stop accepting new work, finish in-flight work, and exit before SIGKILL.

Troubleshooting starts from state and events: get, describe, logs, previous logs, events, and then node/runtime/network checks.

Separate scheduling failures, image pull failures, runtime failures, app failures, and traffic-routing failures so you do not fix the wrong layer.

Operational commands like drain and rollback must respect PDBs, probes, and workload disruption tolerance.

Hands-on example

1. In a non-production namespace, create this safe broken scenario: test SIGTERM handling with preStop and terminationGracePeriodSeconds.

2. Follow a fixed triage order: kubectl get, describe, logs or logs --previous, events, rollout status, node status, and then runtime/network checks.

3. Fix only one variable at a time so the root cause is clear rather than accidentally masked.

4. Save the commands and final diagnosis as an interview-ready incident walkthrough.

Preparing for an interview?

Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.

More Kubernetes, Docker, Helm & Podman interview questions

← All Kubernetes, Docker, Helm & Podman questions