[
https://issues.apache.org/jira/browse/FLINK-38253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18118691#comment-18118691
]
Martijn Visser edited comment on FLINK-38253 at 9/24/26 7:21 AM:
-----------------------------------------------------------------
We won't do this, now that
https://cwiki.apache.org/confluence/spaces/FLINK/pages/449282641/FLIP-607+Migrate+Flink+off+end-of-life+OkHttp+keep+it+off+the+core+classpath
has been voted and accepted
was (Author: martijnvisser):
We won't do this, after
https://cwiki.apache.org/confluence/spaces/FLINK/pages/449282641/FLIP-607+Migrate+Flink+off+end-of-life+OkHttp+keep+it+off+the+core+classpath
has been voted and accepted
> Allow usage of vertx/jdk/jetty/okhttp clients in fabric8 in flink-kubernetes
> ----------------------------------------------------------------------------
>
> Key: FLINK-38253
> URL: https://issues.apache.org/jira/browse/FLINK-38253
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes
> Reporter: Jakub Stejskal
> Priority: Major
> Labels: pull-request-available
>
> Fabric8 allow users to use different http clients implementation - vertx
> (default), okhttp, jetty, jdk. Currently, in Flink okhttp is used. This issue
> is to sync with operator repo where users can switch to different http
> clients via build options - https://issues.apache.org/jira/browse/FLINK-36332.
>
> It was also briefly discuss few weeks ago during fabric8 update -
> https://issues.apache.org/jira/browse/FLINK-38093
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
