[
https://issues.apache.org/jira/browse/FLINK-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492049#comment-17492049
]
Aitozi commented on FLINK-17232:
--------------------------------
After some dig for the [external
IPs|https://kubernetes.io/docs/concepts/services-networking/service/#external-ips].
It seems only comes from the service created with the explicit declaration of
external ip. Currently there is no usage of creating a service with external
IP, Can we safely remove the implicit behavior which use the Service externalIP
as the address of the Endpoint ?
> 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)
