There is currently no automatic verification that user configuration for the Descheduler semantically matches what is configured in the Scheduler (and vice-versa).

For example, if a user enables the `HighNodeUtilization` (bin-packing) Profile in the scheduler operator and the `LifecycleAndUtilization` Profile in the Descheduler, evictions will be attempting to balance resource usage in contrary to the scheduler's attempts at bin packing leading to a constant loop of eviction and scheduling.

The 2 operators should warn in some way if conflicting settings have been enabled. This could be included as the scheduler's dry-run simulation mode.