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

   ### What changes were proposed in this pull request?
   
   This PR aims to publish the existing `KueueEvictionIgnored` warning event 
when Kueue evicts or deactivates the `Workload` of a `SparkApplication` whose 
driver is requested, like a running `SparkCluster` does for a 
`PodsReadyTimeout`.
   
   - A new `AppKueueEvictionStep` reports it from `DriverRequested` to 
`RunningWithBelowThresholdExecutors`. It does not stop or requeue the 
application.
   - The message tells whether the `Workload` still holds its quota (evicted) 
or not (deactivated).
   - Like `KueueAdmissionPending`, the event is republished while it lasts, 
subject to `minIntervalSeconds`.
   
   ### Why are the changes needed?
   
   Currently, an eviction or a deactivation after the driver is requested is 
neither handled nor reported, while the driver and executors keep running. 
Kueue's own events are on the `Workload`, so `kubectl describe 
sparkapplication` shows nothing, although a preempting workload may keep 
waiting for the quota.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No for the released versions, because the Kueue integration is not released 
yet in 
[1.0.0](https://github.com/apache/spark-kubernetes-operator/releases/tag/1.0.0) 
(2026-07-23).
   
   ### 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