Continental Innovates with Rancher and Kubernetes
The gateway to each cluster can have its own port or load balancer, which is unrelated to a service mesh. By default, each Rancher-provisioned cluster has one NGINX ingress controller allowing traffic into the cluster.
You can use the Nginx Ingress controller with or without Istio installed. If this is the only gateway to your cluster, Istio will be able to route traffic from service to service, but Istio will not be able to receive traffic from outside the cluster.
To allow Istio to receive external traffic, you need to enable Istio’s gateway, which works as a north-south proxy for external traffic. When you enable the Istio gateway, the result is that your cluster will have two Ingresses.
You will also need to set up a Kubernetes gateway for your services. This Kubernetes resource points to Istio’s implementation of the ingress gateway to the cluster.
You can route traffic into the service mesh with a load balancer or use Istio’s NodePort gateway. This section describes how to set up the NodePort gateway.
For more information on the Istio gateway, refer to the Istio documentation.
The ingress gateway is a Kubernetes service that will be deployed in your cluster. The Istio Gateway allows for more extensive customization and flexibility.
Result: The gateway is deployed, and will now route traffic with applied rules
We add the BookInfo app deployments in services when going through the Workloads example. Next we add an Istio Gateway so that the app is accessible from outside your cluster.
istio: ingressgateway # use istio default controller
Then to deploy the VirtualService that provides the traffic routing for the Gateway
Result: You have configured your gateway resource so that Istio can receive traffic from outside the cluster.
Confirm that the resource exists by running:
kubectl get gateway -A
The result should be something like this:
To test and see if the BookInfo app deployed correctly, the app can be viewed a web browser using the Istio controller IP and port, combined with the request name specified in your Kubernetes gateway resource:
http://<IP of Istio controller>:<Port of istio controller>/productpage
To get the ingress gateway URL and port,
Result: You should see the BookInfo app in the web browser.
For help inspecting the Istio controller URL and ports, try the commands the Istio documentation.
The official Istio documentation suggests kubectl commands to inspect the correct ingress host and ingress port for external requests.
You can try the steps in this section to make sure the Kubernetes gateway is configured properly.
In the gateway resource, the selector refers to Istio’s default ingress controller by its label, in which the key of the label is istio and the value is ingressgateway. To make sure the label is appropriate for the gateway, do the following: