dongjoon-hyun opened a new pull request, #875: URL: https://github.com/apache/spark-kubernetes-operator/pull/875
### What changes were proposed in this pull request? This PR aims to support `spec.suspend` for a running `SparkCluster` via a new `Suspended` state. - `RunningHealthy` with `spec.suspend=true` moves to `Suspended`, where the operator deletes the master/worker `StatefulSet`s, the worker HPA/PDB, and then the Kueue `Workload` after the pods are gone. - Setting `spec.suspend=false` moves the cluster back to `Submitted` once everything is released, and the cluster is requested again from scratch. - `ClusterInitStep` retries transient API failures (e.g. timeout, `429`, `500`) instead of failing the cluster with the terminal `SchedulingFailure`. ### Why are the changes needed? Currently, `spec.suspend` has no effect on a running `SparkCluster`, so deleting the cluster is the only way to release its resources and its Kueue quota. ### Does this PR introduce _any_ user-facing change? Yes. A running `SparkCluster` can be suspended and resumed, with a new `Suspended` state and `SuspendReleaseFailed` event. ### How was this patch tested? Pass the CIs with the newly added unit tests and E2E tests (`tests/e2e/suspend`, `tests/e2e/kueue`). ### 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]
