[
https://issues.apache.org/jira/browse/FLINK-24947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445753#comment-17445753
]
Yang Wang commented on FLINK-24947:
-----------------------------------
[~spoon-lz] Thanks for creating this ticket. I believe it is a useful feature
especially for unmanaged K8s cluster without good CNI plugin. I appreciate that
you will contribute this work to the community and I could help with reviewing.
Before starting the work, let's figure out some details about the
implementation.
If we enable the host network, then JobManager/TaskManager will be started with
dynamic ports.
# How the TaskManager could find the leader JobManager address after the
JobManager failover without HA?
# How the Flink client could find the leader JobManager address without HA?
# Should we update the internal/external K8s service when the JobManager has
allocated a dynamic port? After then the above two question could be easily
resolved.
> Flink on k8s support HostNetWork model
> --------------------------------------
>
> Key: FLINK-24947
> URL: https://issues.apache.org/jira/browse/FLINK-24947
> Project: Flink
> Issue Type: New Feature
> Components: Deployment / Kubernetes
> Reporter: liuzhuo
> Priority: Minor
>
> For the use of flink on k8s, for performance considerations, it is important
> to choose a CNI plug-in. Usually we have two environments: Managed and
> UnManaged.
> Managed: Cloud vendors usually provide very efficient CNI plug-ins, we
> don’t need to care about network performance issues
> UnManaged: On self-built K8s clusters, CNI plug-ins are usually optional,
> similar to Flannel and Calcico, but such software network cards usually lose
> some performance or require some additional network strategies.
> For an unmanaged environment, if we also want to achieve the best network
> performance, should we support the *HostNetWork* model?
> Use the host network to achieve the best performance
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
