-
Notifications
You must be signed in to change notification settings - Fork 28.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-35394][K8S][BUILD] Move kubernetes-client.version to root pom file #32531
Conversation
Could you review this, @attilapiros ? |
Kubernetes integration test starting |
Kubernetes integration test status failure |
The Python module UT failure is SPARK-35392 and will be fixed in master branch via #32533 . |
Test build #138491 has finished for PR 32531 at commit
|
Hi, @HyukjinKwon . Could you review this PR please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good.
Oh, thank you so much, @viirya ! |
LGTM2 |
Thank you, @HyukjinKwon ! |
LGTM |
Thank you, @attilapiros ! |
…file This PR aims to unify two K8s version variables in two `pom.xml`s into one. `kubernetes-client.version` is correct because the artifact ID is `kubernetes-client`. ``` kubernetes.client.version (kubernetes/core module) kubernetes-client.version (kubernetes/integration-test module) ``` Having two variables for the same value is confusing and inconvenient when we upgrade K8s versions. No. Pass the CIs. (The compilation test passes are enough.) Closes apache#32531 from dongjoon-hyun/SPARK-35394. Authored-by: Dongjoon Hyun <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
What changes were proposed in this pull request?
This PR aims to unify two K8s version variables in two
pom.xml
s into one.kubernetes-client.version
is correct because the artifact ID iskubernetes-client
.Why are the changes needed?
Having two variables for the same value is confusing and inconvenient when we upgrade K8s versions.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs. (The compilation test passes are enough.)