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

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/01/24 09:35:00 UTC

[jira] [Updated] (FLINK-20830) Add a type of HEADLESS_CLUSTER_IP for rest service type

     [ https://issues.apache.org/jira/browse/FLINK-20830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-20830:
-----------------------------------
    Labels: auto-deprioritized-major auto-deprioritized-minor pull-request-available  (was: auto-deprioritized-major auto-deprioritized-minor)

> Add a type of HEADLESS_CLUSTER_IP for rest service type
> -------------------------------------------------------
>
>                 Key: FLINK-20830
>                 URL: https://issues.apache.org/jira/browse/FLINK-20830
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / Kubernetes
>            Reporter: Aitozi
>            Assignee: Aitozi
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor, pull-request-available
>
> Now we can choose ClusterIP or NodePort or LoadBalancer as rest service type. But in our internal kubernetes cluster, there is no kube-proxy, and ClusterIP mode rely on kube-proxy. So I think can we support another type of HEADLESS_CLUSTER_IP to directly talk to jobmanager pod? cc [~fly_in_gis]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)