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

   ### What changes were proposed in this pull request?
   
   This PR documents three missing Spark configurations introduced in Spark 
4.1.0.
   
   | Property | Default | Since | Introduced in |
   | --- | --- | --- | --- |
   | `spark.kubernetes.driver.annotateExitException` | `false` | 4.1.0 | 
[SPARK-53335](https://issues.apache.org/jira/browse/SPARK-53335) (b7f2ab25989) |
   | `spark.kubernetes.executor.useDriverPodIP` | `false` | 4.1.0 | 
[SPARK-53944](https://issues.apache.org/jira/browse/SPARK-53944) (dd8d13b69e8) |
   | `spark.kubernetes.allocation.maxPendingPodsPerRp` | `Int.MaxValue` | 4.1.0 
| [SPARK-53324](https://issues.apache.org/jira/browse/SPARK-53324) 
(9b465a2a9ad) |
   
   ### Why are the changes needed?
   
   Three user-facing Kubernetes configurations added in Spark 4.1.0
   ([SPARK-53324](https://issues.apache.org/jira/browse/SPARK-53324),
   [SPARK-53335](https://issues.apache.org/jira/browse/SPARK-53335),
   [SPARK-53944](https://issues.apache.org/jira/browse/SPARK-53944)) are missing
   from the Running on Kubernetes documentation. Without docs, users cannot
   discover or correctly use them, and there is no single place to confirm the
   default value or `Since Version`.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No. Documentation-only update.
   
   ### How was this patch tested?
   
   Manual review.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Opus 4.7)


-- 
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