Mike Dame
Mike Dame
> > As a workaround, I would like to tell descheduler to ignore pods with label app=myapp in the RemoveDuplicates strategy. > > Ignore from consideration or from eviction? I...
/remove-lifecycle stale
+1, standardizing an interface for each strategy and moving them into their own packages is at the very least a big improvement for our code organization. I would go even...
> Can I attempt both in the same change ? Let's keep different changes to their own PRs. Especially with refactorings like this, if something goes wrong that makes it...
/remove-lifecycle stale /lifecycle frozen
I think it's worth keeping open until we've gotten off of the [migration wrapper](https://github.com/kubernetes-sigs/descheduler/blob/70df89601a943d18f96dad3fd911bea19f10a498/pkg/descheduler/strategy_migration.go#L43)
Mentioned in slack, but I think the solution may be to either: * change the set of nodes passed to the topology spread strategy, or * add logic to the...
@hanumanthan I would go a step further and drop all the redundant prefixes, not just `Remove`, so eg RemovePodsViolatingInterPodAntiAffinity => InterPodAntiAffinity RemovePodsViolatingNodeAffinity => NodeAffinity ... etc the question is if...