Member-only story
Ingress and Istio Gateway Resource
This is an excerpt from Traffic Management with Istio module — you can download the 20+ page PDF and supporting YAML files by signing up at 👉 www.LearnIstio.com 👈
By default, any service running inside the service mesh is not automatically exposed outside of the cluster which means that we can’t get to it from the public Internet. Similarly, services within the mesh don’t have access to anything running outside of the cluster either.
To allow incoming traffic to the frontend service that runs inside the cluster, we need to create an external load balancer first. As part of the installation, Istio creates an istio-ingressgateway service that is of type LoadBalancer and, with the corresponding Istio Gateway resource, can be used to allow traffic to the cluster.
If you run kubectl get svc istio-ingressgateway -n istio-system, you will get an output similar to this one:
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) ....
istio-ingressgateway LoadBalancer 10.107.249.46 <pending> ...The above output shows the Istio ingress gateway of type LoadBalancer. If you’re using a Minikube cluster you will notice how the external IP…
