FoundationKubernetes

What is a Pod, and why do you use a Deployment instead of creating Pods directly?

What they are really testing: Whether you understand the pod as the unit of scheduling and that Deployments add the controller behavior (replicas, self-healing, rollouts) you actually want.

A real interview question

What is a Pod, and why do you use a Deployment instead of creating Pods directly?

What most people say

drag me

A pod is a container, and a Deployment is just a way to create pods.

A pod is not exactly a container (it can hold several and adds shared networking), and "just a way to create pods" misses the whole value: replica management, self-healing, and rollouts.

The follow-ups they ask next

  • What is the relationship between a Deployment, a ReplicaSet, and Pods?

    A Deployment manages ReplicaSets; a ReplicaSet maintains a set of identical Pods. Each rollout creates a new ReplicaSet and scales the old one down, which is how rollback works.

  • When would you put two containers in one pod?

    The sidecar pattern: a helper that must share the pod network/storage, like a log shipper, a proxy, or an init/adapter container. If they can run independently, they belong in separate pods.

What the interviewer is listening for

  • Knows a pod can hold multiple containers sharing the network
  • Explains Deployment = replicas + self-healing + rollouts
  • Knows Deployment manages ReplicaSets

What sinks the answer

  • "A pod is just a container"
  • Creates bare pods in production
  • Unaware of rollout/rollback

If you genuinely do not know

Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.

A pod is [the smallest unit: one or more containers sharing a network namespace and storage, ephemeral]. A bare pod [is not recreated if it dies, no scaling, no rollout]. A Deployment [manages a ReplicaSet that keeps the replica count and self-heals], and gives [declarative rolling updates and rollback]. So it [turns a fragile pod into a resilient, updatable workload].

Keep going with kubernetes

All 336 cloud engineer questions

Knowing the answer is not the same as recalling it under pressure

Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.

Start free