-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-26742][K8S] Update Kubernetes-Client version to 4.1.2 #24002
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
Conversation
|
Please hold this PR until @shaneknapp confirms. Not sure if minikube get updated on Jenkins side. |
|
yep, gonna run these changes manually against the k8s integration tests now. main conversation taking place here: https://issues.apache.org/jira/browse/SPARK-26742 |
|
testing against the 4.1.2 client passed. after i complete the upgrade on the ubuntu workers, i'll approve and trigger this build. |
|
I also successfully finish integration test on v1.10.13 ! I will also try v1.11.7 v1.12.6 and v1.13.3 |
|
ok to test |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
Weird, Looks like that's the same error before upgrade? I didn't see this problem in local testing. |
|
@shaneknapp |
|
Test build #103152 has finished for PR 24002 at commit
|
|
yeah, the k8s/minikube test is supposed to fail as i haven't upgraded those workers yet... i just wanted to make sure that the regular PRB build passed. |
|
@shaneknapp Got you. I don't know they're two different flows. Good to know. :D |
|
@shaneknapp @gatorsmile Look like changes against 2.4 has been closed. Is this one ready to merge? |
|
This can't be merged until the k8s integration tests pass. That would mean they would fail on every other k8s-related PR, and we can't have that. |
|
@vanzin Thanks. I am a little bit confused about test status. It doesn't show any status on my end. PR triggered job fails. But seems it get success later by manual kicked test by @shaneknapp ? This patch passes all tests. @shaneknapp could you take a look? |
|
@vanzin -- these tests won't pass until i upgrade the minikube + k8s versions on the ubuntu workers (which is actually ready to go!). i've tested this PR manually and everything works. regarding #23993 -- i see it's closed but not merged? i checked out the latest spark-2.4.1-rc8 tag and none of the files changed in the 2.4.1 PR show the 4.1.2 k8s client. so...... i guess we're waiting for the spark 2.4.1 cut? |
|
I'm just making a point that this PR should not be merged until the actual, automatic, k8s it run passes. Unless you're willing to manually monitor all k8s-related PRs and manually run integration tests on them, and report the results. |
ah, gotcha. :) it's a matter of timing this w/the 2.4.1 release. do we do the infra/k8s/minikube upgrade before or after the code freezes or wait until afterwards. there was a lot of traffic on dev@ about the 2.4.1 RCs, but this bit may have been lost in the noise. i'll send out an email later and see what people's thoughts are. |
|
@shaneknapp @vanzin Thanks for explanation. Now I get it. |
|
Merging to master (while Shane messes with jenkins). |
What changes were proposed in this pull request?
#23814 was reverted because of Jenkins integration tests failure. After minikube upgrade, Kubernetes client SDK v1.4.2 work with kubernetes v1.13. We can bring this change back.
Reference:
Bump Kubernetes Client Version to 4.1.2
Original PR against master
Kubernetes client upgrade for Spark 2.4
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
Unit Tests:
Please review http://spark.apache.org/contributing.html before opening a pull request.