An init container requests 2 CPU while the two app containers together request 500m. How do init container requests influence Pod scheduling?
Select an answer to reveal the explanation.
Short Explanation
Init containers are the warm-up act that still needs a stage big enough for their gear. Scheduling accounts for init resource needs alongside the running app containers. A hungry init can keep the whole Pod Pending even if the long-running containers look small.
Full Explanation
Kubernetes scheduling accounts for init container resource requirements when placing a Pod. Effective resource calculation considers the maximum of init-container requirements versus the sum of app (and sidecar) container requirements according to current scheduling rules, so oversized init requests can block placement. Init requests are not ignored merely because init containers terminate, and they are not applied only after binding.