Anubhav

We set these two values in the OutlierDetection: ``` consecutive5xxErrors: 0 consecutiveGatewayErrors: 0 ``` And tested the outlier behavior, and observed that traffic stays in the local region, even when...

> Do you mean https://istio.io/latest/docs/reference/config/networking/destination-rule/#LocalityLoadBalancerSetting? The one you mentioned is different. What I am looking for is, be able to define two destinations in virtualservice, which have a matching criteria...

Great, thanks a lot @howardjohn for adding this information, I will test this out with > 1.20. Thanks!

Discussed with @howardjohn and he mentioned that this would be possible even if we do a TLS PASSSTHROUGH on ingressgateway. Will test it out and report back.

Also, we can use this approach, will test this out: 1. For local endpoints, use VirtualServices, so traffic naturally goes there based on locality 2. For remote endpoints, use service...

Thanks for the prompt response! Is istio proxy not marked READY when cluster is in warming state?

But we observed otherwise. We saw a proxy pod come up and return UH / no healthy upstream for STRICT_DNS endpoints. This error subsequently subsided after few seconds.

Related issue on envoyproxy https://github.com/envoyproxy/envoy/issues/14670

@howardjohn - could it be, that envoy did wait for the dns resolution of all STRICT_DNS clusters, but for a few it got a failure, but envoy still went ahead...

Got it. And when this happens, if the request comes for the failed DNS name, it would result in UH / no healthy upstream?