Kubernetes Pod Lifecycle Management

Mon, 12 Oct 2026 00:00:00 +0300

A pod goes through four stages: it is deployed (created and started), it runs (kept healthy), it is updated (replaced by a newer version), and finally it is deleted (shut down gracefully). This article follows a pod through each stage and shows what Kubernetes does, and what you control, at every step.

Key Takeaways

A pod has only five phases: Pending, Running, Succeeded, Failed and Unknown. Everything else you see in kubectl get pods (ContainerCreating, Init:0/1, CrashLoopBackOff, Terminating) is a container state or a kubectl status.
Probes tell Kubernetes whether the app is really healthy: liveness restarts it, readiness takes it out of the Service, startup protects slow starters.
On deletion the app gets SIGTERM, then a grace period (30 s by default), then SIGKILL. Handle SIGTERM, and use a preStop hook when the load balancer needs time to stop sending traffic.
Deployments replace pods step by step; with readiness probes and maxUnavailable: 0, an update doesn’t drop capacity.
Pick the restart policy per workload: Always for services, OnFailure or Never for Jobs.

The Lifecycle on One Page

The whole lifecycle in one picture. Its numbered panels match the sections below, which explain each step in detail with the YAML and the kubectl commands to watch it happen. Click it to open it full size.

Kubernetes on Daniel Corneschi

Kubernetes Pod Lifecycle Management

Key Takeaways

The Lifecycle on One Page