Description of problem: In CNV we are looking at leveraging the LowNodeUtilization strategy of the LifecycleAndUtilization profile to balance out a cluster after upgrade. However, the PodLifeTime is also part of this profile. This will trigger needless VM live migrations every 24hrs, because running pods will be evicted by this strategy. A profile is needed that is exclusively focused on balancing the cluster according to load - spreak retroactively, not proactively. Version-Release number of selected component (if applicable): 4.7 How reproducible: Always Steps to Reproduce: 1. Create a CNV VM, wait 2 days 2. Run descheduler with LifecycleAndUtilization profile 3. Actual results: VM will be rescheduled even if the cluster is balanced Expected results: VM will not be scheduled because the cluster is balanced Additional info:
I commented in https://issues.redhat.com/browse/CNV-10289, but this will likely actually need an RFE to expose any additional settings in the Descheduler Operator
There RFE to track this request https://issues.redhat.com/browse/RFE-1711