dongjoon-hyun opened a new pull request, #908: URL: https://github.com/apache/spark-kubernetes-operator/pull/908
### What changes were proposed in this pull request? This PR aims to clarify the following messages. - The `Failed` state after `SchedulingFailure` of `SparkCluster` points to `SchedulingFailure` for the cause, instead of `Cannot process cluster status.`. - The description of `spark.kubernetes.operator.events.enabled` refers to `configuration.md` instead of listing only some of the events. - `configuration.md` documents the RBAC of K8s events: `get`, `create` and `patch` on `events`. ### Why are the changes needed? - `Cannot process cluster status.` reads as another, unexplained failure. - The description misses 5 of the 13 non-state event reasons. - Users who manage the operator RBAC without the Helm chart need to know these permissions. ### Does this PR introduce _any_ user-facing change? Yes, but only the message of the `Failed` state after `SchedulingFailure` of `SparkCluster` changes from [1.0.0](https://github.com/apache/spark-kubernetes-operator/releases/tag/1.0.0) (2026-07-23). The rest is documentation. ### How was this patch tested? Pass the CIs with the updated test case. ### 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]
