Stil looking for a way to avoid Envoy capturing requests when using direct IP

#1

Hi,

I posted several months ago this: https://github.com/istio/istio/issues/8836

Roughly an injected microservice was trying to reach a Redis master directly by its IP, and this Redis didn’t have Envoy sidecars but it was failing “connection reset by peer”.

On the GitHub issue I received as advice to exclude all my pods (PodCIDR) from Istio list. But since the PodCIDR range is moving after each Kubernetes update, I’m looking for a stable solution.

How could I do to bypass this annoying issue? Is there a way to exclude Istio/Envoy catching requests on port 6379 (Redis port)?

Thank you,

0 Likes