DevOpsInterviews logo
← Containers & Kubernetes / 60
mediumNetflixDatadogMicrosoft

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.

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.

28 answers per topic instead of 18, and your progress kept · no cardor unlock all 401 remaining answers · ₹2,000 / $25
UP NEXT ON YOUR JOURNEY
Next in this trackSidecar-Free Mesh: Ambient and CiliumNext in this trackLoad Balancing the API ServerNext in this trackPod Affinity and Anti-Affinity
NOTES & DISCUSSION · 0

Nothing here yet. Say how you would answer it.