How to unset "retry_host_predicate" using EnvoyFilter? about istio

[ramaraochavali]

Are you sure, with consistent hash, the retry predicate picks another host that does hash based on the hashing config? If yes, it seems like a bug in Envoy

[ktalg]

Are you sure, with consistent hash, the retry predicate picks another host that does hash based on the hashing config? If yes, it seems like a bug in Envoy

I can confirm that Envoy behaves exactly as I describe, but I can't confirm if this is a bug.

there're simply 3 httpbin pods

when I call curl httpbin.infra-al-cn-gdsz-1.svc.cluster.local:8000/status/200 -v -H "xxy: 1"(setting the hash header'xxy'), the istio-proxy container for only one of them prints access log

but when I call curl httpbin.infra-al-cn-gdsz-1.svc.cluster.local:8000/status/503 -v -H "xxy: 1"(returns 503 and triggers retry), two of them print logs

istio ver: 1.11
envoy ver: 1.19

[ktalg]

@ramaraochavali Thank you very much for your MR, but before merging, is there any way to solve the "array merge" problem in encoyFilter?

[ramaraochavali]

AFAIK, It is not possible