Q: What is the Container Runtime Interface (CRI) and what runtimes are commonly used?
CRI is the API between kubelet and the container runtime. kubelet doesn't care what runtime is used as long as it speaks CRI.
#Kubernetes #Additional Kubernetes Scenarios (Q101-Q200) #L3 #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️⃣
Initial Diagnostics & Root Cause Analysis
CRI is the API between kubelet and the container runtime. kubelet doesn't care what runtime is used as long as it speaks CRI.
- containerd — most popular. Lightweight, CNCF project. Used in EKS, AKS, GKE.
- CRI-O — designed specifically for K8s. Used in OpenShift.
- Docker (via dockershim) — removed from K8s 1.24. Docker now uses containerd internally anyway.
2️⃣
Remediation & Permanent Safeguards
Common runtimes: The runtime handles: pulling images, creating/stopping containers, managing namespaces. kubelet just calls CRI APIs.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: containerd — most popular. Lightweight, CNCF project. Used in EKS, AKS, GKE.."
⚡ 60-Second Elevator Pitch Talking Points
- containerd — most popular. Lightweight, CNCF project. Used in EKS, AKS, GKE.
- CRI-O — designed specifically for K8s. Used in OpenShift.
- Docker (via dockershim) — removed from K8s 1.24. Docker now uses containerd internally anyway.
Advertisement