Transit sets an HPA CPU utilization target on a schedules API, but utilization percentages are meaningless without a baseline. What must Pods define for those targets to work?
Select an answer to reveal the explanation.
Short Explanation
CPU utilization is 'how full is the tank versus the tank size you declared.' Without a CPU request, HPA has no denominator for that percentage—set requests so the math works.
Full Explanation
CPU utilization targets for HPA are calculated relative to container CPU requests. Without requests, those percentage-based targets are not meaningful. stdin/tty flags, preStop hooks alone, or emptyDir volumes do not substitute for CPU requests in HPA utilization math.