[ 
https://issues.apache.org/jira/browse/FLINK-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492365#comment-17492365
 ] 

Aitozi edited comment on FLINK-17232 at 2/15/22, 5:15 AM:
----------------------------------------------------------

Let me make it more clear. There are two implicit fallback behavior now
#  If we use loadBalancer type, It will fallback to use \{{NodeIP:NodePort}} as 
restEndpoint when loadBalancer is not ready.
 # It will fallback to use external IP (if there is) when there is no node ip 
or load balancer provided

For the first one I want to open another pr to remove the implicit fallback 
behavior and add a limited block waiting to wait for the ingress IP address to 
be ready. 
For the second one I directly removed in 
[pr|https://github.com/apache/flink/pull/18762].

Please correct me If I missed something [~wangyang0918]



was (Author: aitozi):
Let me make it more clear. There are two implicit fallback behavior now
#  If we use loadBalancer type, It will fallback to use \{{NodeIP:NodePort}} as 
restEndpoint when loadBalancer is not ready.
 # It will fallback to use external IP (if there is) when there is no node ip 
or load balancer provided

For the first one I want to open another pr to remove the implicit fallback 
behavior and add a limited block waiting to wait for the ingress IP address to 
be ready. 
For the second one I directly removed in 
[pr|https://github.com/apache/flink/pull/18762].

Please correct me If I missed something cc [~wangyang0918]


> 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)

Reply via email to