[
https://issues.apache.org/jira/browse/FLINK-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17491971#comment-17491971
]
Aitozi commented on FLINK-17232:
--------------------------------
Hi, when i do some work to refactor the code in
\{{Fabric8FlinkKubeClient#getRestEndpoint}} in
[FLINK-26112|https://issues.apache.org/jira/projects/FLINK/issues/FLINK-26112].
I also confused by this behavior which will fallback to externalIP when
loadBalancer is null. Do you have some suggestion for this cc [~felixzheng]
[~wangyang0918]
> Rethink the implicit behavior to use the Service externalIP as the address of
> the Endpoint
> ------------------------------------------------------------------------------------------
>
> Key: FLINK-17232
> URL: https://issues.apache.org/jira/browse/FLINK-17232
> Project: Flink
> Issue Type: Sub-task
> Components: Deployment / Kubernetes
> Affects Versions: 1.10.0, 1.10.1
> Reporter: Canbin Zheng
> Priority: Major
> Labels: auto-unassigned
>
> Currently, for the LB/NodePort type Service, if we found that the
> {{LoadBalancer}} in the {{Service}} is null, we would use the externalIPs
> configured in the external Service as the address of the Endpoint. Again,
> this is another implicit toleration and may confuse the users.
> This ticket proposes to rethink the implicit toleration behaviour.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
