dongjoon-hyun opened a new pull request, #824:
URL: https://github.com/apache/spark-kubernetes-operator/pull/824

   ### What changes were proposed in this pull request?
   
   This PR upgrades the Kueue `Workload` CRD model from `v1beta1` to `v1beta2`.
   
   - Bump `Constants.KUEUE_API_VERSION` to `v1beta2` and move the model package 
to `org.apache.spark.k8s.operator.kueue.v1beta2`.
   - `WorkloadSpec`: replace `priorityClassName` with `priorityClassRef` (new 
`PriorityClassRef` type with `group`, `kind`, `name`).
   - `Admission`: rename `podSetFlavors` to `podSetAssignments` and replace 
`PodSetFlavors` with `PodSetAssignment` (`name`, `flavors`, `resourceUsage`, 
`count`) to match the `v1beta2` schema.
   - Update `KueueWorkloadFactory` imports and `WorkloadTest` accordingly.
   
   ### Why are the changes needed?
   
   Kueue exposed the `v1beta2` API in 
[v0.15.0](https://github.com/kubernetes-sigs/kueue/releases/tag/v0.15.0) 
(2025-11-28) and switched to `v1beta2` as the storage version in 
[v0.16.0](https://github.com/kubernetes-sigs/kueue/releases/tag/v0.16.0) 
(2026-01-26), with `v1beta1` scheduled to be dropped in an upcoming release 
(already `served: false` in the v0.20.0 release candidate). Since the Kueue 
integration is not released yet, we should start with the current `v1beta2` API 
instead of the deprecated `v1beta1`.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No, the Kueue integration is not released yet.
   
   ### How was this patch tested?
   
   Pass the CIs.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Fable 5.1


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to