dongjoon-hyun opened a new pull request, #920: URL: https://github.com/apache/spark-kubernetes-operator/pull/920
### What changes were proposed in this pull request? This PR aims to simplify the K8s event messages of errors and `SchedulingFailure`. - `EventUtils.describe` uses the message of the API server for a rejected request, like the K8s built-in controllers, instead of the fabric8 message with the request URL and the `Status` dump. It also no longer repeats a cause which reads the same. - The `SchedulingFailure` event describes the failure instead of carrying the stack trace. The resource status keeps the stack trace. - `docs/configuration.md` documents the event messages. ### Why are the changes needed? K8s events reach more readers than the resource status, e.g. via the built-in `view` ClusterRole and event exporters. Stack traces and request URLs are not actionable for them, and they push the actual cause out of the 1024-character event message. ### Does this PR introduce _any_ user-facing change? No, because K8s events have not been released yet. The resource status and the operator log are unchanged. ### How was this patch tested? Pass the CIs with the newly added and updated 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]
