Anubhav

Can we force envoy to do a DNS resolution during runtime, if the DNS resolution had failed earlier?

At runtime? (when envoy receives a request)

> Envoy should retry the dns request if it fails (and if it succeeds) Are you saying this based on the dns refresh rate configuration?

Got it, but can it be forced to do it at runtime if it was not already resolved, (in other words, it would be like adding a retry on no...

I reproduced the issue, with additional monitoring in place, and this is the observation 1. istio proxy made all DNS queries successfully. Validated this by using `curl -s localhost:15000/stats/prometheus |...

> update_failure @yuval-k - don't have the update_failure metric right now. Will get it in the next simulation. Regarding `/clusters` --> I don't see the expected count after envoy becomes...

@yuval-k - will envoy mark itself ready of there was a cluster update failure?

Latest observation: 1. We observed no errors reported by envoy for dns resolution 2. No errors reported by dns server 3. Envoy marks itself ready before making all the STRICT_DNS...

From the data point - derived from dns resolutions, we find that envoy is not making all DNS resolutions before calling itself ready. [update] - validating the above statement via...

Enabled dns:debug on envoy and found that there are a bunch of failed dns resolutions getting logged as: ```bash 2024-01-11T19:15:54.069747Z debug envoy dns external/envoy/source/extensions/network/dns_resolver/cares/dns_impl.cc:153 dns resolution for internal-abcd-1234.us-west-2.elb.amazonaws.com failed with...