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

   ### What changes were proposed in this pull request?
   
   This PR aims to handle an evicted or deactivated Kueue `Workload` before the 
operator requests the driver of a `SparkApplication` or the master of a 
`SparkCluster`.
   
   - A deactivated `Workload` (`spec.active: false`) is kept as it is, and the 
resource waits until it is reactivated.
   - An evicted `Workload` which still holds quota is kept until Kueue's 
requeue backoff (`status.requeueState.requeueAt`) elapses. After that, it is 
deleted to release the quota, and the resource is queued again with a new 
`Workload`.
   - The `KueueAdmissionPending` event describes both waits.
   - The Workload informer now also reconciles on an eviction or a 
(de)activation.
   
   ### Why are the changes needed?
   
   Kueue keeps the admission and the quota of an evicted `Workload` until its 
integration releases it. In contrast, it stops counting a deactivated 
`Workload` right away. Currently, the operator treats both as admitted, so the 
driver or master starts on quota which is about to be taken or is no longer 
counted. An evicted `Workload` which is not admitted yet holds its quota 
forever.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No for the released versions, because the Kueue integration is not released 
yet in v1.0.0.
   
   ### How was this patch tested?
   
   Pass the CIs with the newly added test cases.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Opus 5.5


-- 
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