-
Notifications
You must be signed in to change notification settings - Fork 28.4k
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-44537][BUILD] Upgrade kubernetes-client to 6.8.0 #42142
Conversation
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.
LGTM cc @dongjoon-hyun
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.
+1, LGTM (Pending CIs)
Could you re-trigger the CI once more, @panbingkun ? |
Done. |
Thank you, @panbingkun and all. Merged to master for Apache Spark 4.0. |
### What changes were proposed in this pull request? The pr aims to upgrade kubernetes-client from 6.7.2 to 6.8.0. ### Why are the changes needed? - The newest version brings some bug fixed & improvment, eg: Fix fabric8io/kubernetes-client#5221: Empty kube config file causes NPE Fix fabric8io/kubernetes-client#5281: Ensure the KubernetesCrudDispatcher's backing map is accessed w/lock Fix fabric8io/kubernetes-client#5298: Prevent requests needing authentication from causing a 403 response Fix fabric8io/kubernetes-client#5233: Generalized SchemaSwap to allow for cycle expansion Fix fabric8io/kubernetes-client#5262: all built-in collections will omit empty in their serialized form. - The full release notes: https://github.com/fabric8io/kubernetes-client/releases/ ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass GA. Closes apache#42142 from panbingkun/SPARK-44537. Authored-by: panbingkun <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
What changes were proposed in this pull request?
The pr aims to upgrade kubernetes-client from 6.7.2 to 6.8.0.
Why are the changes needed?
The newest version brings some bug fixed & improvment, eg:
Fix Empty kube config(root/.kube/config) file cause NPE fabric8io/kubernetes-client#5221: Empty kube config file causes NPE
Fix ConcurrentModificationException accessing map in KubernetesCrudDispatcher fabric8io/kubernetes-client#5281: Ensure the KubernetesCrudDispatcher's backing map is accessed w/lock
Fix This change seems to be breaking my application when upgrading from 6.5.0 to 6.5.1? fabric8io/kubernetes-client#5298: Prevent requests needing authentication from causing a 403 response
Fix Support customizable expansion of crd cycles fabric8io/kubernetes-client#5233: Generalized SchemaSwap to allow for cycle expansion
Fix Determine if all built-in collections should omit empty fabric8io/kubernetes-client#5262: all built-in collections will omit empty in their serialized form.
The full release notes:
https://github.com/fabric8io/kubernetes-client/releases/
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA.