⚡ ~/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 175 of 207 in Kubernetes
Senior DevOps / SRE Kubernetes Pod Health & Self-Healing Core Architecture
🎯 Target Role / Context: Kubernetes Pod Lifecycle & Resiliency

Q: What are the different types of probes, and which probe acts first — Startup, Readiness, or Liveness?

Detailed breakdown of the Kubernetes health probe evaluation lifecycle, explaining why startupProbe runs first and how readiness and liveness interact to prevent deployment death spirals.

#Kubernetes #Health Probes #Liveness #Readiness #Startup #Comparisons
🎙️ Candidate Opening & Architectural Context
"Kubernetes provides three distinct health probes: Startup, Readiness, and Liveness. The Startup probe ALWAYS acts first. Until the Startup probe succeeds, both Liveness and Readiness probes are completely disabled."
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 provides three distinct health probes: Startup, Readiness, and Liveness. The Startup probe ALWAYS acts first. Until the Startup probe succeeds, both Liveness and Readiness probes are completely disabled.

1

The Execution Hierarchy (Startup Probe Acts First)

On container launch, the kubelet runs the startupProbe. While it runs, liveness and readiness probes do not execute. If the startup probe fails to succeed within initialDelaySeconds + (periodSeconds * failureThreshold), the container is killed and restarted.

2

Readiness Probe: Controls Traffic Routing

Once startup passes, the readinessProbe executes periodically. If it fails, the container is NOT restarted. Instead, the kubelet removes the Pod IP from the Service EndpointSlice so it stops receiving user traffic.

Advertisement
3

Liveness Probe: Controls Container Lifecycle (Self-Healing)

The livenessProbe detects deadlocks where the process is running but cannot make progress. If it fails, the kubelet kills the container and invokes the restartPolicy.

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"StartupProbe executes first to protect slow-booting apps. Readiness removes pods from service endpoints without killing them; Liveness kills and restarts frozen containers."
⚡ 60-Second Elevator Pitch Talking Points
  • StartupProbe acts first: all readiness and liveness checks are disabled until it succeeds.
  • ReadinessProbe controls routing: failure strips the pod IP from Endpoints without restarting the container.
  • LivenessProbe controls restarts: failure triggers container termination (SIGTERM/SIGKILL) for deadlocks.
  • Use startupProbe with high failureThreshold for legacy apps instead of huge initialDelaySeconds.
⛔ 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. Over-granting cluster-admin permissions to pod ServiceAccounts instead of scoping namespace Roles when configuring Kubernetes Health Probe Over-granting cluster-wide permissions violates least-privilege principles and allows compromised pods to escalate privileges across namespaces.
  2. Referencing mutable latest container tags across production Kubernetes Deployment specs when configuring Kubernetes Health Probe Deployments referencing :latest risk inconsistent versions across replica pods and break deterministic rollback capabilities.
  3. Omitting pod readiness probes, causing traffic to hit uninitialized application containers when configuring Kubernetes Health Probe Readiness probes gate traffic delivery; missing probes cause Kubernetes to route user requests to pods before dependencies or caches are loaded.
  4. Executing diagnostic triage without analyzing chronological cluster events and describe outputs when configuring Kubernetes Health Probe Cluster events provide sequential timestamps of scheduler decisions, probe failures, and image pull timeouts essential for rapid root-cause isolation.
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 →