[SPARK-55709][K8S][TESTS] Fix ExecutorLifecycleTestUtils.persistentVolumeClaim to use ReadWriteOncePod instead of ReadWriteOnce#54507
Closed
dongjoon-hyun wants to merge 1 commit intoapache:masterfrom
Closed
Conversation
…to use `ReadWriteOncePod` instead of `ReadWriteOnce`
dongjoon-hyun
changed the title
ExecutorLifecycleTestUtils.persistentVolumeClaim to use ReadWriteOncePod instead of ReadWriteOnceExecutorLifecycleTestUtils.persistentVolumeClaim to use ReadWriteOncePod instead of ReadWriteOnce
LuciferYang
approved these changes
Feb 26, 2026
sarutak
approved these changes
Feb 26, 2026
Member
Author
|
Thank you, @LuciferYang and @sarutak . Merged to master. |
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
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 fix
ExecutorLifecycleTestUtils.persistentVolumeClaimto useReadWriteOncePodinstead ofReadWriteOnce.Why are the changes needed?
Since Apache Spark 4.0.0, we used
ReadWriteOncePodby default. We should test the Apache Spark's behavior consistently.MountVolumesFeatureStepto useReadWriteOncePodinstead ofReadWriteOnce#44817spark.kubernetes.legacy.useReadWriteOnceAccessModefor old K8s clusters #44985Does this PR introduce any user-facing change?
No, this is a test case change.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
Generated-by:
Gemini 3.1 Pro (High)onAntigravity