⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Kubernetes Interview Questions Scenario 64 of 207 in Kubernetes
Senior DevOps / SRE [L2] Kubernetes Advanced Scenarios Production Scenario [L2]

Q: What is the difference between liveness and readiness probes? Give a scenario where each is important.

Liveness probe — "is this container still alive?" If it fails, Kubernetes restarts the container. Use for detecting deadlocks or infinite loops where the process is running but not making progress.

#Kubernetes #Advanced Scenarios #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
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? KodeKloud's CKA & CKAD Hands-On Certification Track covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: "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."

1️⃣

Initial Diagnostics & Root Cause Analysis

Key: failed liveness = restart. Failed readiness = remove from load balancer rotation, but don't restart.

  • Liveness probe — "is this container still alive?" If it fails, Kubernetes restarts the container. Use for detecting deadlocks or infinite loops where the process is running but not making progress.
  • Scenario: A Java app has a thread deadlock. The JVM is running but requests hang forever. Liveness probe detects no HTTP response → restarts container.
  • Readiness probe — "is this container ready to serve traffic?" If it fails, the pod is removed from Service endpoints. Use for apps that need warmup time or temporarily can't serve (e.g., during a DB connection retry).
2️⃣

Remediation & Permanent Safeguards

  • Scenario: App just started and is loading a 5GB ML model. Readiness fails until load completes. No traffic is sent yet. App is not restarted (liveness probe is fine).
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Liveness probe — "is this container still alive?" If it fails, Kubernetes restarts the container. Use for detecting deadlocks or i."
⚡ 60-Second Elevator Pitch Talking Points
  • Liveness probe — "is this container still alive?" If it fails, Kubernetes restarts the container....
  • Scenario: A Java app has a thread deadlock. The JVM is running but requests hang forever. Livenes...
  • Readiness probe — "is this container ready to serve traffic?" If it fails, the pod is removed fro...
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Enabling Horizontal Pod Autoscaler without defining baseline container CPU and memory requests HPA computes target metrics based on resource requests; omitting requests leaves HPA unable to calculate utilization percentages.
  2. Configuring restrictive container CPU limits that trigger severe CFS scheduler throttling Aggressive CPU limits throttle container execution cycles, causing unexpected p99 latency spikes even when total node CPU is underutilized.
  3. Leaving automountServiceAccountToken enabled by default on pods with no API interaction needs Automounting API tokens exposes internal cluster credentials to pods that have no operational requirement to interact with kube-apiserver.
  4. Configuring StatefulSets using shared static PersistentVolumeClaims instead of volumeClaimTemplates in kubernetes-q052-what-is-the-difference-between-live volumeClaimTemplates guarantee dedicated independent storage volumes for each ordinal replica pod in stateful clusters.
Advertisement
📥 FREE DOWNLOAD · 101-PAGE COMPANION HANDBOOK
Studying for Kubernetes & SRE Technical Rounds?
Download the complete 100-question PDF field guide covering all 11 core modules with offline diagnostic runbooks.
📥 Download PDF (Free) Read Online Guide →
Want more Kubernetes scenarios?
Explore our complete collection of scenario-based Kubernetes interview runbooks.
Browse All Kubernetes Questions →