-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Bump kubernetes-client-bom from 6.3 to 6.4 #30480
Conversation
5af9817
to
9832047
Compare
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.
That's awesome! You can also add the exclusion to the bom/application
pom.xml
Ah but we only import the kubernetes-bom there, nevermind |
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.
Awesome!
As a followup, I will try to remove okhttp from the BOM as it shouldn't be a dependency anymore.
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.
I think it's safe to remove OkHttp from the list of managed dependencies too:
https://github.com/quarkusio/quarkus/blob/main/bom/application/pom.xml#L171-L172
and
https://github.com/quarkusio/quarkus/blob/main/bom/application/pom.xml#L4169-L4183
Guillaume will followup the Okhttp/Okio removal in a separate PR
Yeah I think it's better to do it in a separate PR in case it breaks something and we have to revert it. |
This comment has been minimized.
This comment has been minimized.
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.
Very glad to see this!
An example of the enforcer failures:
|
9832047
to
381c6c4
Compare
381c6c4
to
4820013
Compare
941ebf9
to
239ae37
Compare
It seems that we might need to bump Dekorate along with the client. |
Including @Sgitario for awareness |
14d8677
to
d5ac934
Compare
162d311
to
ee6b651
Compare
Signed-off-by: Marc Nuri <[email protected]>
- Switch to use Vert.x HttpClient implementation Signed-off-by: Marc Nuri <[email protected]>
Signed-off-by: Marc Nuri <[email protected]>
Signed-off-by: Marc Nuri <[email protected]>
ee6b651
to
9d5d197
Compare
Don't worry about the Gradle tests failing, it's unrelated to your patch. |
Thx. Yes, I discussed internally with Georgios. I've rebased after the merge of #30758. Hoping this time we get a completely green report 🤞 . |
This comment has been minimized.
This comment has been minimized.
✔️ The latest workflow run for the pull request has completed successfully. It should be safe to merge provided you have a look at the other checks in the summary. |
With quarkusio#30480, we no longer depend on okhttp, so there is no reason to keep it in the BOM anymore
With quarkusio#30480, the k8s client no longer uses OkHttp
With quarkusio#30480, the k8s client no longer uses OkHttp
Kubernetes Client
6.4.06.4.1 was just released: https://github.com/fabric8io/kubernetes-client/releases/tag/v6.4.1This release of the client includes the new Vert.x
HttpClient
implementation. This PR includes changes in thepom.xml
files to make use of this client instead of the defaultOkHttp
implementation. If everything goes well, this should fix #29520OkHttpthat thekubernetes-httpclient-okhttp
module is not mistakenly propagated, however, I'm not sure this is the right place. I can't directly block OkHttp since it is also used (server-side) in the MockServer./cc @metacosm @maxandersen @shawkins @gastaldi @geoand
Fix #30558