Istio has an Ingress gateway, which is a reverse proxy that's implemented through Envoy. The purpose of Ingress is to allow access to services from outside the cluster. As shown in the following diagram, external inbound and outbound communication goes through configured Ingress and Egress gateways:
As we can see, Microservice A (for example, microservice-a.mynamespace.cluster.local:9085) is exposed to internet domain names such as www.example.com:443 through the Istio Ingress gateway. The client TLS (short for Transport Layer Security) termination is done at the Ingress gateway.
For incoming as well as outgoing requests, the Ops ...
