Q: What is a pause container and why is it in every pod?
The "infra container" or "sandbox container" that holds the network namespace for the pod. All containers in the pod join its network nam...
#Kubernetes #Additional Kubernetes Scenarios (Q101-Q200) #L2 #Container Orchestration #K8s
🎙️ Candidate Opening & Architectural Context
""Kubernetes is a declarative desired state system; understanding the reconciliation loop is how you diagnose this quickly. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Production Solution & Architecture
The "infra container" or "sandbox container" that holds the network namespace for the pod. All containers in the pod join its network namespace (that's how they share localhost). If the app container dies and restarts, the network namespace (and IP address) is preserved because the pause container keeps running. Image: pause:3.x (few hundred KB). Managed by containerd/CRI-O, not visible in kubectl get pods. Q121-Q150. More Kubernetes Rapid-fire
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: The "infra container" or "sandbox container" that holds the network namespace for the pod. All containers in the pod join its netw."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: The "infra container" or "sandbox container" that holds the network namespace for the pod. All
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement