Configure Istio Ingress Gateway

Until now, you used a Kubernetes Ingress to access your application from the outside. In this module, you configure the traffic to enter through an Istio ingress gateway, in order to apply Istio control on traffic to your microservices.

  1. Store the name of your namespace in the NAMESPACE environment variable. You will need it to recognize your microservices in the logs:

    $ export NAMESPACE=$(kubectl config view -o jsonpath="{.contexts[?( == \"$(kubectl config current-context)\")].context.namespace}")
    $ echo $NAMESPACE
  2. Create an environment variable for the hostname of the Istio ingress gateway:

    $ export MY_INGRESS_GATEWAY_HOST=istio.$
  3. Configure an Istio ingress gateway:

    $ kubectl apply -f - <<EOF
    kind: Gateway
      name: bookinfo-gateway
        istio: ingressgateway # use Istio default gateway implementation
      - port:
          number: 80
          name: http
          protocol: HTTP
    kind: VirtualService
      name: bookinfo
      - bookinfo-gateway.$NAMESPACE.svc.cluster.local
      - match:
        - uri:
            exact: /productpage
        - uri:
            exact: /login
        - uri:
            exact: /logout
        - uri:
            prefix: /static
        - destination:
            host: productpage
              number: 9080
  4. Set INGRESS_HOST and INGRESS_PORT using the instructions in the Determining the Ingress IP and ports section.

  5. Add the output of this command to your /etc/hosts file:

  6. Access the application’s home page from the command line:

    $ curl -s $MY_INGRESS_GATEWAY_HOST:$INGRESS_PORT/productpage | grep -o "<title>.*</title>"
    <title>Simple Bookstore App</title>
  7. Paste the output of the following command in your browser address bar:

    $ echo http://$MY_INGRESS_GATEWAY_HOST:$INGRESS_PORT/productpage
  8. Simulate real-world user traffic to your application by setting an infinite loop in a new terminal window:

    $ while :; do curl -s <output of the previous command> | grep -o "<title>.*</title>"; sleep 1; done
    <title>Simple Bookstore App</title>
    <title>Simple Bookstore App</title>
    <title>Simple Bookstore App</title>
    <title>Simple Bookstore App</title>
  9. Check the graph of your namespace in the Kiali console (The URL should be in your /etc/hosts file that you set previously).

    This time, you can see that traffic arrives from two sources, unknown (the Kubernetes Ingress) and from istio-ingressgateway istio-system (the Istio Ingress Gateway).

    Kiali Graph Tab with Istio Ingress Gateway
    Kiali Graph Tab with Istio Ingress Gateway
  10. At this point you can stop sending requests through the Kubernetes Ingress and use Istio Ingress Gateway only. Stop the infinite loop (Ctrl-C in the terminal window) you set in the previous steps. In a real production environment, you would update the DNS entry of your application to contain the IP of Istio ingress gateway or configure your external Load Balancer.

  11. Delete the Kubernetes Ingress resource:

    $ kubectl delete ingress bookinfo
    ingress.extensions "bookinfo" deleted
  12. In a new terminal window, restart the real-world user traffic simulation as described in the previous steps.

  13. Check your graph in the Kiali console. After about a minute, you will see the Istio Ingress Gateway as a single source of traffic for your application.

    Kiali Graph Tab with Istio Ingress Gateway as a single source of traffic
    Kiali Graph Tab with Istio Ingress Gateway as a single source of traffic

You are ready to configure logging with Istio.

Was this information useful?
Do you have any suggestions for improvement?

Thanks for your feedback!