concept Istio Ingress gateway in category microservice

appears as: Istio Ingress gateway, The Istio Ingress gateway, Istio Ingress gateway
Microservices Security in Action

This is an excerpt from Manning's book Microservices Security in Action.

The Istio Ingress gateway (with no SDS support) reads the public/private key pair for the TLS communication from a well-defined Kubernetes Secret called istio-ingressgateway-certs. In fact, the Istio Ingress gateway is an Envoy proxy, running within a Pod, under the istio-system namespace, in the Kubernetes cluster. You can run the following command to list all the Pods available in the istio-system namespace and find the name of the Istio Ingress gateway Pod. The output of the command is truncated to show only the Istio Ingress gateway Pod:

All the communications between the curl client and the microservices now happen via the Ingress gateway. Let’s run the following two commands to find the external IP address and the HTTPS port of the Istio Ingress gateway, which runs under the istio-system namespace. The first command finds the external IP address of the istio-ingressgateway Service and exports it to the INGRESS_HOST environment variable, and the second command finds the HTTPS port of the istio-ingressgateway Service and exports it to the INGRESS_HTTPS_PORT environment variable. If you use a local Kubernetes deployment on Docker Desktop with no load balancer, then instead of the external IP, you need to use the node IP address (probably 127.0.0.1) along with the corresponding port (probably 443):

\> export INGRESS_HOST=$(kubectl -n istio-system \

get service istio-ingressgateway \
-o jsonpath='{.status.loadBalancer.ingress[0].ip}')

\> export INGRESS_HTTPS_PORT=$(kubectl -n istio-system \
get service istio-ingressgateway \
-o jsonpath='{.spec.ports[?(@.name=="https")].port}')
Figure 12.4 STS issues a JWT access token to the client application, and the client application uses it to access the Order Processing microservice on behalf of the user, Peter. The Order Processing microservice uses the same JWT it got from the client application to access the Inventory microservice. The Istio Ingress gateway intercepts all the requests coming to the microservice and terminates the TLS connection.
sitemap

Unable to load book!

The book could not be loaded.

(try again in a couple of minutes)

manning.com homepage
test yourself with a liveTest