[jira] [Closed] (FLINK-17232) Rethink the implicit behavior to use the Service externalIP as the address of the Endpoint

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

     [ https://issues.apache.org/jira/browse/FLINK-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yang Wang closed FLINK-17232.
-----------------------------
    Fix Version/s: 1.16.0
       Resolution: Fixed

Fixed via:

master: 0ff1e40540c788fdc967e5f91c170b08b59a9c48

> 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
>            Assignee: Aitozi
>            Priority: Major
>              Labels: auto-unassigned, pull-request-available, stale-assigned
>             Fix For: 1.16.0
>
>
> 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.7#820007)