dongjoon-hyun opened a new pull request, #831:
URL: https://github.com/apache/spark-kubernetes-operator/pull/831

   ### What changes were proposed in this pull request?
   
   This PR aims to publish K8s events for all `SparkApplication` and 
`SparkCluster` state transitions, not only for failure states. The reason of 
each event is the new state name.
   
   | Type | `SparkApplication` | `SparkCluster` |
   |---|---|---|
   | `Warning` | `SchedulingFailure`, `Failed`, `DriverEvicted`, 
`DriverStartTimedOut`, `DriverReadyTimedOut`, `ExecutorsStartTimedOut`, 
`RunningWithBelowThresholdExecutors`, `TerminatedWithoutReleaseResources` | 
`SchedulingFailure`, `Failed` |
   | `Normal` | All other states | All other states |
   
   An event is published only when the current state changes. Repeated 
transitions into the same state increment the count of one `Event` object.
   
   ### Why are the changes needed?
   
   To make the full lifecycle of Spark resources visible via `kubectl describe` 
and `kubectl get events`.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No by default. When `spark.kubernetes.operator.events.enabled` is `true`, 
the operator also publishes the new `Normal` and `Warning` events above.
   
   ### How was this patch tested?
   
   Pass the CIs with the newly added unit tests.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Opus 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]

Reply via email to