[
https://issues.apache.org/jira/browse/FLINK-38093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004931#comment-18004931
]
Mate Czagany commented on FLINK-38093:
--------------------------------------
Since Fabric8 has switched to Vert.x as the default HTTP implementation instead
of OkHttp, we need to make a decision here:
h3. Switch from OkHttp to Vert.x
* According to Fabric8, it's more performant than OkHttp. It should use less
resources than OkHttp, but I think it will be a very small difference for
Flink. Might be useful for the Flink Kubernetes Operator though
* Some companies have internal policies to exclude Kotlin dependencies, which
OkHttp pulls (FLINK-36332)
* Vert.x has a transitive dependency of Netty, and our current version
(4.1.100.Final) is not compatible. We will need to upgrade it
* Vert.x is licensed under both the Eclipse Public License 2.0 (EPL-2.0) and
the Apache License 2.0, so it can be included without a problem
h3. Stay with OkHttp
* OkHttp is still supported by Fabric8, and will continue to be in the future
* We still need Vert.x as a test dependency, as `kubernetes-server-mock` uses
that, so a Netty upgrade is still needed (or we need to override every Netty
package version in flink-kubernetes for the test scope)
No matter the decision, flink-kubernetes needs to have a newer Netty versions
in its `test` scope after upgrading to Fabric 7.x
> Update version of Fabric8 to 7.3.1
> ----------------------------------
>
> Key: FLINK-38093
> URL: https://issues.apache.org/jira/browse/FLINK-38093
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes
> Reporter: Mate Czagany
> Priority: Major
>
> Fabric8 should be updated to the latest version to get the latest
> improvements and bug fixes available.
> It should be investigated whether it's worth it to use Vert.x, the new
> default HTTP library used by Fabric8 and drop OkHttp.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
