Sarthak Agarwal

If I understand this correctly, the descheduler should run with separate profiles if they want different nodeSelector? ``` apiVersion: "descheduler/v1alpha2" kind: "DeschedulerPolicy" profiles: # Profile 1: For worker nodes only...

Looking at the docs it seems like profile right now does have a nodeSelector config >create your own Evictor Plugin or use the Default one provided by Descheduler. Other uses...

> > Looking at the docs it seems like profile right now does have a nodeSelector config > > > create your own Evictor Plugin or use the Default one...

My intention behind this all is to run HighNodeUtilization only on nodes which can't be removed by cluster-autoscaler maybe due to local-storage or whatever. Meanwhile all other plugins can run...