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
Is your feature request related to a problem? Please describe.
I saw that descheduler calculates the Mem usage of Pod to get the actual usage MEM on each machine, but this will ignore the memory usage of some programs running directly on the host
Describe the solution you'd like
so , can we provide a feature that balances the load from the node MEM dimension?
The text was updated successfully, but these errors were encountered:
Getting the actual memory usage requires access to metrics, and I'm not sure if even those metrics will report on programs running outside of k8s. Either way, we do already have an issue open to try implementing metrics-based real usage evictions: #225. I think this is a duplicate of that, do you agree @Kuri-su ?
Is your feature request related to a problem? Please describe.
I saw that
descheduler
calculates the Mem usage of Pod to get the actual usage MEM on each machine, but this will ignore the memory usage of some programs running directly on the hostDescribe the solution you'd like
so , can we provide a feature that balances the load from the node MEM dimension?
The text was updated successfully, but these errors were encountered: