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

   ### What changes were proposed in this pull request?
   
   This PR aims to check the driver pod phase (`Failed` / `Succeeded`) before 
the empty-`containerStatuses` guard in 
`BaseAppDriverObserver.observeDriverTermination`.
   
   ### Why are the changes needed?
   
   A driver pod can fail before any container starts, for example because of 
PodGC after node deletion or eviction under `DiskPressure`. It then has `phase: 
Failed` and empty `containerStatuses`. The operator treated this pod as 
pending, so the app stayed in `DriverRequested` until the driver start timeout. 
If the timeout was disabled, it stayed there forever.
   
   - https://github.com/apache/spark-kubernetes-operator/issues/863
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes. Such an app now moves to `Failed` or `DriverEvicted` right away instead 
of `DriverStartTimedOut`.
   
   ### How was this patch tested?
   
   Pass the CIs with the newly added `AppDriverReadyObserverTest`.
   
   ### 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]

Reply via email to