<p>I would recommend to remove Nginx Ingress from the equation. Although it's possible to use Nginx Ingress with Istio, it makes zero sense to do that since it adds an unnecessary hop and extra logic which will be difficult to troubleshoot. Istio is more than enough to deliver traffic to your app.</p>
<p>Other than that your traffic diagram looks valid.</p>

CC BY-SA 4.0
2024-05-06T22:32:13.157Z
2024-05-06T22:32:13.157Z
Vasilii Angapov
<p>I have a app running on k8s with istio as service mesh and nginx as ingress controller. I wonder what would be the request flow to my service. Is it possibly like so:</p>
<pre><code>user-request --&gt;istio_gateway --&gt; istio_virtualServive --&gt; istio_destinationRoute --&gt; nginx_ingress --&gt; service_pod .
</code></pre>
<p>Any suggestions / insights?</p>

<docker><kubernetes><nginx><istio>
How do Istio Gateway ,VirtualService ,DestinationRule works together to fullfill a request?
user45187
# How do Istio Gateway ,VirtualService ,DestinationRule works together to fullfill a request?

(Asked by: username_0 on 2024-05-06)

I have a app running on k8s with istio as service mesh and nginx as ingress controller. I wonder what would be the request flow to my service. Is it possibly like so:
user-request -->istio_gateway --> istio_virtualServive --> istio_destinationRoute --> nginx_ingress --> service_pod .

Any suggestions / insights?

**Tags:** docker, kubernetes, nginx, istio


---

## 1 answers

### Answer by username_1 on 2024-05-06. Score: 0

I would recommend to remove Nginx Ingress from the equation. Although it's possible to use Nginx Ingress with Istio, it makes zero sense to do that since it adds an unnecessary hop and extra logic which will be difficult to troubleshoot. Istio is more than enough to deliver traffic to your app.

Other than that your traffic diagram looks valid.


---

