Amir Alavi
Amir Alavi
/lgtm Thank you 🏆
fyi- Warning should land in v0.30 and should be noted in the release notes: https://github.com/kubernetes-sigs/descheduler/pull/1337
/remove-lifecycle stale
Adding @ingvagabund's proposal in this Issue: At the same time someone might ask for disabling only specific checks. So instead of defining a bool argument I would like to suggest...
Is there a way to make this "future proof" in case we decide to pull in Scheduler's Filter extension point?
@logyball would you please create a new Issue? We can implement this as a patch without the need for re-design of NodeFit
linking another PR: https://github.com/kubernetes-sigs/descheduler/pull/1144
/remove-lifecycle stale
/remove-lifecycle stale
/reopen /remove-lifecycle rotten