A Pod is the smallest deployable unit — one or more containers that share a network namespace (same IP, can talk over localhost) and storage volumes, always scheduled together on one node.

You rarely create bare Pods directly; controllers like Deployments manage them so they’re recreated if they die. Multiple containers in a Pod are for tightly- coupled helpers — a sidecar (log shipper, proxy) — not separate applications.

Key Pod concepts: resource requests/limits (CPU/memory), probes (liveness/readiness), and restart policy. Pods are ephemeral — their IPs change, which is why Services exist.

apiVersion: v1
kind: Pod
metadata:
  name: web
spec:
  containers:
    - name: nginx
      image: nginx:1.27
      ports: [{ containerPort: 80 }]
      resources:
        requests: { cpu: "100m", memory: "128Mi" }
        limits:   { cpu: "500m", memory: "256Mi" }
      readinessProbe:
        httpGet: { path: /, port: 80 }

kubectl apply -f pod.yaml
kubectl get pods
kubectl describe pod web
kubectl logs web

1. Write a minimal Pod manifest running an nginx container.
2. Add CPU/memory requests and limits and explain the difference.
3. Add a readiness probe and describe what it controls.
4. Explain why you’d use a Deployment rather than a bare Pod.

• ↗ Kubernetes — Pods