You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2020/12/08 06:41:09 UTC
[jira] [Updated] (FLINK-17232) Rethink the implicit behavior to use
the Service externalIP as the address of the Endpoint
[ https://issues.apache.org/jira/browse/FLINK-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Metzger updated FLINK-17232:
-----------------------------------
Fix Version/s: (was: 1.12.0)
1.13.0
> 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: Canbin Zheng
> Priority: Major
> Fix For: 1.13.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.3.4#803005)