Anubhav

> > > The intent behind this is that without outlierDetection, we cannot detect failing workloads, so will never failover at all. IE its not "failover" just "only send to...

Is there a feature we can add to ensure this behavior and not depend on the outlierDetection:{} to disable outlier and enable locality LB?

Plus do other scenarios like distribute work as expected with `outlierDetection: {}` ?

> What is your intended behavior? Traffic _never_ leaves the zone? "Failover" without an ability to ever failover (due to missing unhealthy concept) seems unexpected. > > Distribute has no...

> What is your intended behavior? Traffic _never_ leaves the zone? "Failover" without an ability to ever failover (due to missing unhealthy concept) seems unexpected. > > Distribute has no...

> > Will locality based weighted LBs work as expected without outlier detection configured > > This is a limitation imposed by envoy, not istio > > > // Under...

Can we not rely on the [loadbalancerLB.enabled flag](https://istio.io/latest/docs/reference/config/networking/destination-rule/#LocalityLoadBalancerSetting) ?

@hzxuzhonghu - Yes, that can be done, but for that one has to maintain the destinationrules in each region with the right distribute configuration. @ramaraochavali - but setting priorities is...

@ramaraochavali - yes, understood that. my question was istio should still set priorities irrespective of whether outlier configuration is set or not (given that loadBalancerLB.enabled flag is set to true.

> For now the only way is `outlierDetection: {}`. I cannot promise 100%, but I would imagine this will not likely go away even if it was unintended originally. Hey...