[SPARK-48076][K8S] Promote KubernetesVolumeUtils to DeveloperApi
#46326
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
Member
Author
|
Could you review this PR, @viirya ? This is for |
Member
Author
|
Could you review this PR, @HyukjinKwon ? |
HyukjinKwon
approved these changes
May 2, 2024
Member
Author
|
Thank you, @HyukjinKwon ! |
Member
Author
|
Merged to master for Apache Spark 4.0.0. |
Member
Author
|
Thank you, @viirya ! |
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 promote
KubernetesVolumeUtilstoDeveloperApifrom Apache Spark 4.0.0 for Apache Spark Kubernetes Operator.Why are the changes needed?
This API was added by the following at
Apache Spark 3.0.0and has been stable.Since
Apache Spark Kubernetes Operatorrequires this, we had better maintain it as a developer API officially fromApache Spark 4.0.0.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.