[
https://issues.apache.org/jira/browse/FLINK-16601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303160#comment-17303160
]
hayden zhou commented on FLINK-16601:
-------------------------------------
Yes， NodePort support is very useful for self-buit k8s cluter.
> Correct 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: Sub-task
> Components: Deployment / Kubernetes
> Affects Versions: 1.10.0
> Reporter: Canbin Zheng
> Assignee: Canbin Zheng
> Priority: Major
> Fix For: 1.13.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 the master node
> does not expose a NodePort for the NodePort Service.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
