DevOpsInterviewPrep logo
← Containers & Kubernetes / 48
mediumNewNetflixDatadogMicrosoft

The HPA shows a CPU number. Trace it from the container to the scaling decision, and tell me where that number lies.

Kubelet resource metrics to metrics-server to aggregated API to HPA controller: every hop adds lag and averaging. Walking the path and naming where it distorts demand separates operators from dashboard readers.

Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.

Kubelet resource metrics to metrics-server to aggregated API to HPA controller: every hop adds lag and averaging. Walking the path and naming where it distorts demand separates operators from dashboard readers.

20 answers per topic instead of 10, and your progress kept · no cardor unlock all 390 remaining answers · ₹2,000 / $25
UP NEXT ON YOUR JOURNEY
Next in this trackSidecar proxies cost us real memory per pod. Do ambient and Cilium-style meshes actually remove that cost, and what do they trade?Next in this trackHow do you load balance the Kubernetes control plane, and what breaks first when every client points at one API server endpoint?Next in this trackThree replicas of one service landed on the same node and one reboot killed them all. How do affinity and anti-affinity actually work?
DISCUSSION · 0

Nothing here yet. Say how you would answer it.