[
https://issues.apache.org/jira/browse/FLINK-17231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Canbin Zheng updated FLINK-17231:
---------------------------------
Description:
Currently, if people use the LB Service, when it comes to retrieving the
Endpoint for the external Service, we make an implicit fallback immediately to
return the NodePort address and port if we fail to get the LB address in a
single try. This kind of toleration can confuse the users since the NodePort
address/port may be unaccessible due to some reasons like network security
policy, and the users may not know what really happen behind.
This ticket proposes to always return the LB address/port otherwise throw an
Exception indicating that the LB is unready or abnormal.
was:
Currently, if people use the LB Service, when it comes to retrieving the
Endpoint for the external Service, we make an implicit fallback immediately to
return the NodePort address and port if we fail to get the LB address in a
single try. This kind of toleration can confuse the users since the NodePort
address/port maybe unaccessible due to some reasons like network security
policy, and the users may not know what really happen behind.
This ticket proposes to always return the LB address/port otherwise throw an
Exception indicating that the LB is unready or abnormal.
> Deprecate possible implicit fallback from LB to NodePort When retrieving
> Endpoint of LB Service
> -----------------------------------------------------------------------------------------------
>
> Key: FLINK-17231
> URL: https://issues.apache.org/jira/browse/FLINK-17231
> Project: Flink
> Issue Type: Sub-task
> Components: Deployment / Kubernetes
> Affects Versions: 1.10.0, 1.10.1
> Reporter: Canbin Zheng
> Priority: Major
> Fix For: 1.11.0
>
>
> Currently, if people use the LB Service, when it comes to retrieving the
> Endpoint for the external Service, we make an implicit fallback immediately
> to return the NodePort address and port if we fail to get the LB address in a
> single try. This kind of toleration can confuse the users since the NodePort
> address/port may be unaccessible due to some reasons like network security
> policy, and the users may not know what really happen behind.
> This ticket proposes to always return the LB address/port otherwise throw an
> Exception indicating that the LB is unready or abnormal.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
