You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/07/07 22:38:00 UTC

[jira] [Updated] (FLINK-17231) Deprecate possible implicit fallback from LB to NodePort When retrieving Endpoint of LB Service

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

Flink Jira Bot updated FLINK-17231:
-----------------------------------
    Labels: auto-unassigned pull-request-available stale-assigned  (was: auto-unassigned pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issue is assigned but has not received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a comment updating the community on your progress.  If this issue is waiting on feedback, please consider this a reminder to the committer/reviewer. Flink is a very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone else may work on it.


> 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
>            Assignee: liuzhuo
>            Priority: Major
>              Labels: auto-unassigned, pull-request-available, stale-assigned
>
> 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.20.10#820010)