[SPARK-48722][K8S] Patch executor pod without optimistic locking #47102
+1
−0
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 support apache spark patch executor pod without optimistic locking when using version 6.5 or later of fabric8 kubernetes-client, to avoid error 409 conflicts when other components attempts to patch requests to the same executor pod.
Why are the changes needed?
Before fabric8 kubernetes-client#6.5,
edit
action without optimistic locking by default. Request is following:After fabric8 kubernetes-client#6.5,
edit
action with optimistic locking. Request is following:More info: fabric8io/kubernetes-client#4896
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual test with k8s auditing log.
Was this patch authored or co-authored using generative AI tooling?
No.