dongjoon-hyun opened a new pull request, #923: URL: https://github.com/apache/spark-kubernetes-operator/pull/923
### What changes were proposed in this pull request? This PR aims to recommend the Spark native `spark.driver.timeout` instead of the Kueue `kueue.x-k8s.io/max-exec-time-seconds` label in `docs/spark_custom_resources.md`, with a link to the existing `examples/pi-with-driver-timeout.yaml`. https://github.com/apache/spark-kubernetes-operator/blob/1d07c7f1f255d0223121e7e26e56113fd0106bf1/examples/pi-with-driver-timeout.yaml#L24-L25 ### Why are the changes needed? The operator does not copy the label to the `Workload`. Even if it did, the deactivation which Kueue applies after that time is not honored for a running `SparkApplication`, so its driver and executors would keep running while Kueue no longer counts their quota. On the other hand, `spark.driver.timeout` with `DriverTimeoutPlugin` is available in all supported Spark versions (4.0+) and stops the driver itself, so the attempt releases its `Workload` like any other stopped attempt. ### Does this PR introduce _any_ user-facing change? No. This is a documentation-only change for the Kueue integration, which 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? Manual review. ### 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]
