mirror of
https://github.com/outbackdingo/kubernetes.git
synced 2026-01-28 02:19:27 +00:00
4ca47255a8
When pod-level resources are detected, the cpu and memory manages cannot engage because the feature is not yet compatible, one of the main reasons being the managers only work at container level. So, the managers has to detect if pod level resources are in use, and turn themselves to no-operation skipping resource allocation should that be the case. We add an intentional loud log to inform the user, because pods with pod-level resources landing on a node which cannot actuate the desired spec is likely to be undesirable. Signed-off-by: Francesco Romani <fromani@redhat.com>