Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warnings in Log #860

Open
Garfield96 opened this issue Jul 13, 2022 · 1 comment
Open

Warnings in Log #860

Garfield96 opened this issue Jul 13, 2022 · 1 comment

Comments

@Garfield96
Copy link

Describe the bug
There are a lot of messages in the cri logs stating:

cri-resmgr[]: W: [resource-manager] UpdateContainerResources: XXX TODO: we probably should reallocate the container instead...
cri-resmgr[]: W: [resource-manager] UpdateContainerResources: silently dropping container update request for <container name>

Does this mean the current configuration is not yet implemented or can these warnings be ignored?

Expected behavior
No warnings.

To Reproduce

Environment

Additional context

@klihub
Copy link
Contributor

klihub commented Aug 8, 2022

Currently (without non-disruptive vertical pod autoscaling in use) this is a symptom of the node's kubelet running with CPUManager enabled and configured with a policy other than none (IOW, static). The CPUManager has a reconcilation loop which is periodically sending update requests for all containers running on the node. CRI Resource Manager ignores these.

Please check your cluster's/kubelet's configuration and set the built-in CPU policy to none.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants