[
https://issues.apache.org/jira/browse/FLINK-20830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aitozi updated FLINK-20830:
---------------------------
Description: 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] (was: 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 we can support
another type of HEADLESS_CLUSTER_IP to directly talk to jobmanager pod, what's
your suggestion? cc [~fly_in_gis])
> 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)
