You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When calculating a pod's requests, we don't seem to consider the initContainers.
There could be a case where the initContainer requests are larger than the regular container requests. In this case, the scheduler will use the initContainer's requests over the regular container requests.
Resources
Given the ordering and execution for init containers, the following rules for resource usage apply:
The highest of any particular resource request or limit defined on all init containers is the effective init request/limit
The Pod's effective request/limit for a resource is the higher of:
the sum of all app containers request/limit for a resource
the effective init request/limit for a resource
Scheduling is done based on effective requests/limits, which means init containers can reserve resources for initialization that are not used during the life of the Pod.
The text was updated successfully, but these errors were encountered:
When calculating a pod's requests, we don't seem to consider the initContainers.
There could be a case where the initContainer requests are larger than the regular container requests. In this case, the scheduler will use the initContainer's requests over the regular container requests.
See https://kubernetes.io/docs/concepts/workloads/pods/init-containers/#resources
The text was updated successfully, but these errors were encountered: