Mike Dame
Mike Dame
Sorry for the delay @Dentrax I think that this could be a good aspect of a potential refactor for the descheduler to make it more like a "descheduler framework". I'm...
@Dentrax sure thing, it never hurts to send a poc PR to get some more detail discussion rolling. Thanks!
/remove-lifecycle stale /lifecycle frozen
@Dentrax thanks for bumping this. This is definitely one of the features we had in mind with the framework refactor. You're right that this will be an execution-level change rather...
Based on the reactions it sounds like this is something people are interested in. I'd like to bring it up at tomorrow's sig-scheduling meeting if anyone would like to discuss...
> or this needs to be approached as one whole issue? We don't want to do this as one whole issue, but rather with atomic changes. Additionally, each change should...
@ingvagabund sounds good! thanks for working out the next steps. For step 4, the v1alpha2 configuration should be backward-compatible with v1alpha1 configs, so no plugins should be dependent on v1alpha1....
> Conversion from v1alpha2 to v1alpha1 will be possible only when there's a single profile the framework code only needs to convert v1alpha1 -> v1alpha2, such as when the user...
Yeah, there's no need to convert v1alpha2 to v1alpha1 (and like you said, it's probably not even possible). Just 1->2 to handle legacy configs, which should be possible
Thank you for starting this work @hanumanthan. From a quick overview this looks to be the right direction but I will give it a more in depth review when I...