Interview Kubernetes, Docker, Helm & Podman

What is a Pod, and why does Kubernetes schedule Pods rather than containers?

Kubernetes, Docker, Helm & Podman · Basic level

Answer

A Pod is the smallest deployable unit in Kubernetes. Kubernetes schedules Pods rather than individual containers because containers inside a Pod share the same lifecycle, network namespace, volumes, and placement requirement.

Technical explanation

Containers in a Pod share an IP and ports, so localhost communication works between containers in the same Pod.

Pod co-location should be used for tightly coupled containers, not as a replacement for independent microservices.

Kubernetes resources are declarative API objects; controllers continuously drive actual state toward spec.

The practical interview angle is to connect the concept to reliability: scheduling, healing, scaling, rollout safety, and clear ownership.

Use kubectl get, describe, explain, and -o yaml to move from high-level view to exact spec/status details.

Hands-on example

1. Create a local lab with kind or minikube, then use it to demonstrate: create a two-container Pod sharing localhost and an emptyDir volume.

2. Run kubectl get nodes -o wide, kubectl get pods -A, kubectl describe, and kubectl get -o yaml to connect the concept to actual cluster state.

3. Make one intentional change, such as a label change, image update, or replica change, and watch how the control plane reconciles it.

4. Capture the command output and convert it into an interview story: desired state, observed state, failure mode, and fix.

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