You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2022/01/25 02:29:00 UTC

[jira] [Commented] (FLINK-24947) Support host network for native K8s integration

    [ https://issues.apache.org/jira/browse/FLINK-24947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17481501#comment-17481501 ] 

Yang Wang commented on FLINK-24947:
-----------------------------------

Fixed via:

master:

c7219f8827016d1067f008e2324c0194dad65cb1

36e98b33408cff77886ecd2280fa0e5f79033191

> Support host network for native K8s integration
> -----------------------------------------------
>
>                 Key: FLINK-24947
>                 URL: https://issues.apache.org/jira/browse/FLINK-24947
>             Project: Flink
>          Issue Type: New Feature
>          Components: Deployment / Kubernetes
>            Reporter: liuzhuo
>            Assignee: liuzhuo
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>
> 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)