[
https://issues.apache.org/jira/browse/FLINK-15795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17085379#comment-17085379
]
Yang Wang commented on FLINK-15795:
-----------------------------------
[~felixzheng] I post the yesterday discussion[1] here since this ticket is
related. If you want to completely separate the {{getRestEndpoint}} for
{{LoadBalancer}} and {{NodePort}}, this ticket should be taken into account.
Just to make sure that we print a proper and accessible JobManager url in the
Flink client log. Given that the rest port is configured to 8081.
* For LoadBalancer, it should be {{LB_IP:8081}}. If we do not get a LB_IP,
then it will great if a warning log shows up.
* For NodePort, it should be {{K8S_MASTER:NodePort}} or {{K8s_NODE:NodePort}}.
[1]. https://github.com/apache/flink/pull/11715#discussion_r409295087
> KubernetesClusterDescriptor seems to report unreachable JobManager interface
> URL
> --------------------------------------------------------------------------------
>
> Key: FLINK-15795
> URL: https://issues.apache.org/jira/browse/FLINK-15795
> Project: Flink
> Issue Type: Sub-task
> Components: Deployment / Kubernetes
> Affects Versions: 1.10.0
> Reporter: Till Rohrmann
> Priority: Minor
> Fix For: 1.10.1, 1.11.0
>
>
> The {{KubernetesClusterDescriptor}} reports the {{JobManager}} web interface
> URL when deploying the cluster. In my case (using almost the standard
> configuration), it reported an unreachable URL which consisted of the K8s
> cluster's endpoint IP. This might be a configuration problem of the K8s
> cluster but at the same time, the descriptor deployed a LoadBalancer (default
> configuration) through which one could reach the web UI. In this case, I
> would have wished that the {{LoadBalancer's}} IP and port is reported instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
