dongjoon-hyun opened a new pull request, #916: URL: https://github.com/apache/spark-kubernetes-operator/pull/916
### What changes were proposed in this pull request? This PR aims to write K8s events with a Kubernetes client which does not retry a failed request. - `ConfigurableEventRecorder.withDefaultSink` uses `KubernetesClientFactory.withoutRetries`, which is moved from `KueueWorkloadUtils` for reuse. The derived client keeps the connections, the interceptors and the request timeout of the operator client. - `ReconcileError` is published on every retry, subject to `spark.kubernetes.operator.events.minIntervalSeconds`, instead of only on the first attempt, so that a dropped first write does not hide the whole failure. - `docs/configuration.md` is updated accordingly. ### Why are the changes needed? `DefaultEventSink` writes events synchronously on the reconciliation thread. By default, the fabric8 client retries a write which fails with `429`, `5xx` or an I/O error up to 10 times with backoff. So, a single event write can hold a reconciliation for tens of seconds exactly when the API server is in trouble and error events are published. Since a failed event write is only logged anyway, there is no need to retry it. ### Does this PR introduce _any_ user-facing change? No for the released versions, because K8s Events support 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 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]
