[
https://issues.apache.org/jira/browse/FLINK-16601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060585#comment-17060585
]
Yang Wang commented on FLINK-16601:
-----------------------------------
Hi [~felixzheng], thanks for you response.
Usually when the users expect to use {{NodePort}} to expose the service, we
assume that the firewall and network security policy have been configured
correctly. However, i have asked our internal K8s guys, and we have some cases
that needs to use the master address to generate the {{NodePort}} url because
of network security policy.
So could we add a new config option to control whether to use master or slave
nodes to generate the {{NodePort}} url? I think the default behavior could be
randomly selecting one from slave nodes.
> Corret the way to get Endpoint address for NodePort rest Service
> ----------------------------------------------------------------
>
> Key: FLINK-16601
> URL: https://issues.apache.org/jira/browse/FLINK-16601
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Affects Versions: 1.10.0
> Reporter: Canbin Zheng
> Priority: Major
> Fix For: 1.11.0
>
>
> Currently, if one sets the type of the rest-service to {{NodePort}}, then the
> way to get the Endpoint address is by calling the method of
> 'KubernetesClient.getMasterUrl().getHost()'. This solution works fine for the
> case of the non-managed Kubernetes cluster but not for the managed ones.
> For the managed Kubernetes cluster setups, the Kubernetes masters are
> deployed in a pool different from the Kubernetes nodes and do not expose
> NodePort for a NodePort Service.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
