<p>I have been using Ambassador for a while, I like it but it's been spamming my logs with <code>GET /api/.ambassador-internal/openapi-docs</code>. So I'm thinking to switch to another mapping alternative and I found Istio. I'm not sure what exactly what is yet, but seems like I can use it to replace ambassador mapping.</p>
<p>So my question is that if I use Istio do I even need Ambassador?</p>

<p><a href="https://github.com/datawire/ambassador" rel="noreferrer">Ambassador</a> is essentially a Kubernetes ingress controller/API gateway that uses <a href="https://www.envoyproxy.io/" rel="noreferrer">Envoy</a>.</p>
<p>And Istio is a service mesh that happens to have its own <a href="https://istio.io/latest/docs/tasks/traffic-management/ingress/ingress-control/" rel="noreferrer">ingress mechanism</a>, and Istio also uses Envoy as sidecar proxies. So in a way yes, you can replace Ambassador with Istio, but you may not be able to get the API gateway type of features with Istio. <a href="https://blog.christianposta.com/microservices/do-i-need-an-api-gateway-if-i-have-a-service-mesh/" rel="noreferrer">This blog</a> explains the differences and attempts to clarify the confusion.</p>
<p>I'm not really sure that Istio is going to help you with the logs since it looks like the issue that you are seeing with log spamming is related to the API gateway component. It really depends on how you architect your application/services.</p>
