[
https://issues.apache.org/jira/browse/FLINK-20830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17258943#comment-17258943
]
Yang Wang commented on FLINK-20830:
-----------------------------------
I am not pretty sure whether a Kubernetes cluster without kube proxy is a
typical use case. But I just feel it is harmless to support this. I have one
concern about the config option. Since {{HEADLESS_CLUSTER_IP}} is not a
concrete service type[1], we have to process it specifically.
[1].
https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types
> 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
> Priority: Major
>
> 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.3.4#803005)
