Code Room
On-callMediumoc-g027
Subject SaturationLevel Mid–Senior~30 minCommon in Reliability & on-call interviewsIndustries Technology, Software development

Question

An image-thumbnailing service (Go) runs on Kubernetes. After a routine traffic increase (a marketing push doubled uploads), p99 latency degraded badly and requests started timing out, but per-pod CPU utilization shown in your dashboard reads only ~55% — nowhere near 100%. The HPA isn't scaling up because it's targeting 70% CPU and 55 < 70. The pod has `resources.limits.cpu: 1` and `requests.cpu: 0.5`. The container metric `container_cpu_cfs_throttled_periods` is high and rising. Triage and mitigate.

What a strong answer looks like

Stop the bleeding first (mitigate), then form hypotheses from real signals. Separate root cause from symptom, communicate status as you go, and close with what prevents a repeat.

Diagram & narrate the incident
Loading whiteboard…
Run or narrate your approach, then ask the coach.