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

   ### What changes were proposed in this pull request?
   
   This PR aims to update `docs/architecture.md` to reflect the current code.
   
   - **Cluster State Transition**: Remove the transitions that can never be 
taken (`RunningHealthy --> Failed` and all `ResourceReleased` transitions) and 
add the missing `SchedulingFailure --> Failed`. Clarify that cluster resources 
are garbage collected only when the CR is deleted.
   - **Application State Transition**: Add the missing transitions, such as 
`Succeeded --> ScheduledToRestart` (`RestartPolicy.Always`) and 
`TerminatedWithoutReleaseResources --> ResourceReleased` (retain duration 
exceeded). Also describe the driver termination/eviction transitions, the 
driver ready timeout, and the actual owner reference chain.
   - **Deployment Topology**: Show that worker pods are created by the 
operator, and fix the multi-instance requirement to distinct `ClusterRole` / 
`ClusterRoleBinding` names.
   
   ### Why are the changes needed?
   
   The document did not match the code, as pointed out in 
https://github.com/apache/spark-kubernetes-operator/pull/866#discussion_r4079981163.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No behavior change. This is a documentation-only fix.
   
   ### How was this patch tested?
   
   Manual review against the code. Also passed `markdownlint` and rendered all 
mermaid diagrams with `mmdc`.
   
   ### 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