02Your service autoscales on CPU and still falls over during traffic spikes. Why, and what would you scale on instead?▼hardNewFlipkartUberAmazon2 repliesunlockedTurns the standard autoscaling definition into the problem it actually causes. Almost every candidate can define an HPA; far fewer can say why theirs did not save them.Open full answer →
12HPA and VPA on the same deployment: why is that a problem, and what should you run instead?▼mediumNewDatabricksUberSAP2 replies○ sign inA specific configuration trap with a clean explanation. Both controllers act on the same signal from opposite directions, and the result oscillates.Open full answer →
37CPU metrics lag demand by minutes because traffic arrives as queue depth. How should autoscaling react to events?▼mediumNewPhonePeSwiggyFlipkart◆ premiumUtilization-based scaling is the wrong sensor when work arrives as backlog. The design questions are threshold math against drain rate, reaction-time bounds from polling, and why lag-driven fleets oscillate without generous targets and idempotent consumers.Open full answer →
48The HPA shows a CPU number. Trace it from the container to the scaling decision, and tell me where that number lies.▼mediumNewNetflixDatadogMicrosoft◆ premiumKubelet 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.Open full answer →
