[jira] [Commented] (FLINK-15795) KubernetesClusterDescriptor seems to report unreachable JobManager interface URL

["Yang Wang (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-15795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17028808#comment-17028808 ] 

Yang Wang commented on FLINK-15795:
-----------------------------------

Just like what we have describe in the [documentation|https://ci.apache.org/projects/flink/flink-docs-master/ops/deployment/native_kubernetes.html#accessing-job-manager-ui]. Since the cloud provider and Kubernetes needs some time to prepare the load balancer, you may get a {{NodePort}} JobManager Web Interface in the client log. You can use {{kubectl get services/<ClusterId>}} to get EXTERNAL-IP and then construct the load balancer JobManager Web Interface manually {{http://<EXTERNAL-IP>:8081}}.

> 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.11.0, 1.10.1
>
>
> 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)