Understand Service Mesh (Istio) via Guide 3 about term-project-cloudriven HOT 1 CLOSED

Istio – Service Mesh

Our platform extends Kubernetes by installing Istio, a service mesh. Istio works by injecting a second container into every pod. This injected container, referred to as a sidecar, monitors the network traffic into and out of the pod.

Pre-requisite

1. AWS EKS cluster should be up and running which will serve the 4 microservices, db (database service), s1 (user service), s2 (music service), and s3 (playlist service).
   a. Starting a fresh EKS cluster.
   make -f eks.mak start

2. Ensure AWS DynamoDB is initialized. The tables have to be available for db (database service) to serve the other 3 microservices. (s1/s2/s3)
   aws dynamodb list-tables

3. Provision the cluster. This includes;
   a. Create a namespace within the cluster in which applications will be placed.
   kubectl create ns c756ns
kubectl config set-context --current --namespace=c756ns
   b. Provision the Kubernetes cluster. This includes “Installing Istio”, “Installing Prometheus stack by calling obs.mak recursively”, and “Deploying and monitoring the four microservices”.
   make -f k8s.mak provision

4. Run the following command to install kiali
   make -f obs.mak install-kiali

5. Get the Grafana and kiali URL using the following command.
   make -f k8s.mak grafana-url
make -f k8s.mak kiali-url

6. Generate traffic into the cluster using the gatling scripts.
   $ ./gatling-1-user.sh
$ ./gatling-5-music.sh

The Kiali graph

Using the controls, configure the graph as follows (controls listed starting at top left, proceeding left to right):
• Namespaces: c756ns
• Graph type: Versioned app graph
• Display interval: Last 1m
• Refresh interval: Every 30s
• Display:
o Show Edge Labels: Traffic Rate
o Show: Compressed Hide, Operation Nodes, Service Nodes, Traffic Animation
o Show Badges: Virtual Services
The two leftmost nodes in the graph are labelled istio-ingressgateway and unknown. These are where incoming requests enter the mesh.
Requests entering from istio-ingressgateway are from outside the cluster. All the requests made by the Gatling simulations enter via this node.
The unknown node is Prometheus. Requests from this node are requests for metrics values, one per node every 30 seconds. Prometheus is listed as unknown because in our configuration it is not included in the mesh.

from term-project-cloudriven.