You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2021/01/19 15:42:17 UTC

[GitHub] [flink] wangyang0918 edited a comment on pull request #14692: [FLINK-20944][k8s] Do not resolve the rest endpoint address when the service exposed type is ClusterIP

wangyang0918 edited a comment on pull request #14692:
URL: https://github.com/apache/flink/pull/14692#issuecomment-762900776


   Both the detached/attached mode for application, the submission process does not need to create a `RestClusterClient`. Currently, we only use the `RestClusterClient` to print the web monitor address in `KubernetesClusterDescriptor`.
   
   The problem is that Flink client does not know whether it is running in or out of the K8s cluster. So it is hard to not create the `RestClusterClient` and tell the users that they should not use the `flink cancel/list` out of the K8s cluster when using `ClusterIP` setting. Maybe we could add a log to remind users that the rest endpoint(e.g. webui, cancel, list, etc.) could only be used in the K8s cluster when service is exposed with `ClusterIP`.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org