[SPARK-53913][DOCS] Document newly added K8s configurations #52618
+34
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
cc @peter-toth |
dongjoon-hyun
force-pushed
the
SPARK-53913
branch
from
275ebbf to
a86b22a
Compare
zhengruifeng
approved these changes
Oct 15, 2025
|
Thank you, @zhengruifeng ! |
|
Merged to master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR aims to document newly added K8s configurations as a part of Apache Spark 4.1.0 preparation.
Why are the changes needed?
To sync the document with K8s
Config.scala. For now, three PRs added four configurations.spark.kubernetes.(driver|executor).pod.excludedFeatureSteps#51522spark.kubernetes.executor.terminationGracePeriodSeconds#51811spark.kubernetes.allocation.maximum#52615Does this PR introduce any user-facing change?
No behavior change. This is only adding new configuration documents.
How was this patch tested?
Manual review.
Was this patch authored or co-authored using generative AI tooling?
No.