Michał Woźniak

/assign @gabesaba who is already looking into it

/remove-lifecycle rotten

https://github.com/kubernetes-sigs/kueue/pull/4813 already addresses the issue when `preemption.reclaimWithinCohort: Any` is used, and it was cherrypicked to [0.11](https://github.com/kubernetes-sigs/kueue/pull/4822) and [0.10](https://github.com/kubernetes-sigs/kueue/pull/4823). Solving the generic issue when `preemption.reclaimWithinCohort: LowerPriority` is much trickier because when...

> Indeed, the blocker for this feature request was mostly resolved by JobManagedBy feature and almost major Job integrations like Kubeflow and Ray support the managedBy functionality as well. Yeah,...

/remove-lifecycle stale

I think @IrvingMg @mszadkow has a lot of experience setting up MultiKueue so can easily check that Basically, we can have one CQ using MultiKueue and on the same cluster...

I'm also fine with either integration or e2e tests, I would probably suggest to start with integration tests as easier to write and debug, and see where we are.

> or maybe it's cleared after the job is finished?) Yes, we only count non-finished admitted workloads: https://github.com/kubernetes-sigs/kueue/blob/main/apis/kueue/v1beta2/clusterqueue_types.go#L541 says **Number of admitted workloads that haven't finished yet**

@mszadkow please also update the documentation to say that the hybrid mode is supported. By hybrid (or role sharing) we mean the manager cluster taking the role of the manger,...

Let's start with KEP update for this. /retitle MultiKueue KEP update to introduce MultiKueue Dispatcher API /release-note-edit ```release-note NONE ```