dongjoon-hyun opened a new pull request, #910: URL: https://github.com/apache/spark-kubernetes-operator/pull/910
### What changes were proposed in this pull request? This PR aims to handle a Kueue `PodsReadyTimeout` eviction of a running `SparkCluster` like any other eviction, instead of only reporting it by the `KueueEvictionIgnored` warning event. - The cluster enters `Suspended`, releases its master and workers, and is queued again with a new `Workload` after Kueue's requeue backoff, even if its pods are ready by now, like the Kueue built-in integrations. - `KueueEvictionIgnored` is published only for a `SparkApplication`. - A cluster whose pods are stuck terminating releases its `Workload` when the requeue backoff elapses, instead of after the 30-minute hold interval. - The Kueue E2E test runs with a shortened requeue backoff (10 seconds). ### Why are the changes needed? SPARK-59803 ignored a `PodsReadyTimeout` of a running `SparkCluster` only because the operator did not record `PodsReady` yet, which SPARK-59846 added. An ignored eviction is never released, so a preempting workload waits for its quota forever, and with `blockAdmission`, a cluster whose pods never get ready holds back every other workload. ### 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]
