[SPARK-52606] Promote Spark CRDs to v1
#261
Closed
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
dongjoon-hyun
force-pushed
the
SPARK-52606
branch
from
aa2a153 to
7455116
Compare
viirya
approved these changes
Jun 28, 2025
Member
Author
|
Thank you, @viirya . Merged to main. |
Member
Author
|
cc @jiangzho , @peter-toth , too. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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
Spark CRDsfromv1beta1tov1at Apache Spark K8s Operator0.5.0. After finalizing CRDs tov1, we are going to start to prepareApache Spark K8s Operator 1.0release.Why are the changes needed?
To show the maturity of these CRDs according to K8s API versioning.
due to increased risk of bugs and lack of long-term support
The support for a feature will not be dropped, though the details may change.
Does this PR introduce any user-facing change?
We support all
v1alpha,v1beta1, andv1because they are identical.How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.