☂️ Release 0.18 plan

[mimowo]

The release is planned tentatively for 18th May, let's discuss the scope.

Nice to haves:

• Concurrent Admission (Alpha) #8691
• Workload Scheduling Constraints (Workload-Level) and Preference-Aware MultiKueue Dispatching #8729
• Add Prometheus metrics for Cohort to report resource usage, quota, workload counts #7539
• Support for running hero workloads #8826
• Add native Kueue support for ReplicaSets and Deployments #6334
• Support guaranteed minimum runtime before fair sharing preemption #9876
• Historical Usage Fair Sharing: half-life based score for cohort-level scheduling and preemption #9734
• Path to Beta for ElasticJobsViaWorkloadSlices - Ray Autoscaling #8651
• Support DRA Partitionable Devices (KEP-4815) in Kueue #10108
• Flavor-Aware Fair Sharing for Heterogeneous Resources (Weighted flavours) #8902
• Provide a way to specify in the configuration what resources kueue will manage #7513

[mimowo]

cc @tenzen-y @gabesaba @kannon92 @sohankunkerkar @mwysokin @mukund-wayve @ichekrygin @amy

[kannon92]

Its harder than we thought to get our users to convert from v1beta1 to v1beta2.

I wanted to ask if we can keep serving v1beta1 for 0.18.

And maybe stop serving in 0.19.

[mimowo]

Thank you for the valuable feedback @kannon92 , I think we will continue serving v1beta1 along with v1beta2 in 0.18. We re-consider dropping in 0.19/0.20

[tenzen-y]

Thank you for the valuable feedback @kannon92 , I think we will continue serving v1beta1 along with v1beta2 in 0.18. We re-consider dropping in 0.19/0.20

I’m also fine with postponing v1beta1 removal to 0.19.

[sohankunkerkar]

Thanks @mimowo for creating this tracking issue. I’d also like to include #8243 in this plan, as it acts as an umbrella issue for promoting the top-level Kueue + DRA feature gate to beta.