[
https://issues.apache.org/jira/browse/FLINK-16601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17059892#comment-17059892
]
Yang Wang commented on FLINK-16601:
-----------------------------------
You are right. If deploying on a managed K8s cluster, especially in the cloud
environment, it will be a problem to use master address as {{NodePort}}. So
what do you suggest to change? If we use kube slave node address instead, it
will not be very convenient for unmanaged K8s cluster. Because we need to
configure external ip for slave nodes and firewalls to allow network traffic
outside of the K8s cluster.
> 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)
