Istio overview in Microservices - Architecture Diagram

System Overview - Istio overview

Istio is a service mesh that helps manage communication between microservices. It provides traffic management, security, and observability without changing application code.

Key requirements include secure service-to-service communication, load balancing, and monitoring of microservice interactions.

Architecture Diagram

User
  |
  v
Ingress Gateway
  |
  v
Envoy Sidecar Proxy <--> Istio Control Plane
  |                      |
  v                      v
Microservice A <-------> Microservice B
       |                     |
       v                     v
   Database               Cache

Components

User

client

Sends requests to microservices

Ingress Gateway

gateway

Entry point for external traffic into the service mesh

Envoy Sidecar Proxy

proxy

Intercepts and manages all network traffic for a microservice

Istio Control Plane

control_plane

Manages configuration and policies for proxies

Microservice A

service

Business logic service A

Microservice B

service

Business logic service B

Database

database

Stores persistent data

Cache

cache

Speeds up data access for microservices

Request Flow - 11 Hops

User → Ingress Gateway

Ingress Gateway → Envoy Sidecar Proxy

Envoy Sidecar Proxy → Istio Control Plane

Envoy Sidecar Proxy → Microservice A

Microservice A → Cache

Cache → Microservice A

Microservice A → Database

Database → Microservice A

Microservice A → Envoy Sidecar Proxy

Envoy Sidecar Proxy → Ingress Gateway

Ingress Gateway → User

Failure Scenario

Component Fails:Istio Control Plane

Impact:Proxies cannot get updated configuration or policies, but existing connections continue working

Mitigation:Control plane is usually deployed with replicas for high availability; proxies cache last known config

Architecture Quiz - 3 Questions

Which component manages the configuration and policies for the proxies?

A Istio Control Plane

B Ingress Gateway

C Envoy Sidecar Proxy

D Database

Design Principle

Istio uses a sidecar proxy pattern to transparently manage microservice communication, enabling features like traffic control and security without changing application code. The control plane centralizes configuration, while proxies enforce policies locally, ensuring scalability and flexibility.

Practice

1. What is the primary role of Istio in a microservices environment?

easy

A. Compile microservices code into executables

B. Store data for microservices in a database

C. Manage communication between microservices with security and monitoring

D. Build user interfaces for microservices

Solution

1. Step 1: Understand Istio's purpose

   Istio is designed to manage how microservices talk to each other, adding security, monitoring, and control.

2. Step 2: Eliminate unrelated options

   Storing data, building interfaces, or compiling code are not Istio's functions.

3. Final Answer:

   Manage communication between microservices with security and monitoring -> Option C

4. Quick Check:

   Istio manages microservice communication = D [OK]

Hint: Istio controls microservice communication and security [OK]

Common Mistakes:

• Confusing Istio with a database
• Thinking Istio builds UI
• Assuming Istio compiles code

2. Which command is used to install Istio on a Kubernetes cluster?

easy

A. kubectl apply -f istio.yaml

B. istioctl install

C. docker run istio/install

D. helm install istio

Solution

1. Step 1: Identify Istio installation method

   Istio is installed using the official Istio CLI tool with istioctl install.

2. Step 2: Check other options

   kubectl apply -f applies Kubernetes configs but Istio recommends istioctl. docker run and helm install are not standard for Istio installation.

3. Final Answer:

   istioctl install -> Option B

4. Quick Check:

   Istio installed with istioctl = A [OK]

Hint: Use istioctl tool to install Istio on Kubernetes [OK]

Common Mistakes:

• Using kubectl apply without istioctl
• Trying to install Istio with docker run
• Assuming Helm is default for Istio

3. Given the command kubectl get pods -n istio-system, what output indicates Istio sidecar proxies are injected correctly?

medium

A. Pods show two containers: one for the app and one named 'istio-proxy'

B. Pods show only one container with the app name

C. Pods are in CrashLoopBackOff state

D. Pods are not listed at all

Solution

1. Step 1: Understand sidecar injection

   Istio injects a sidecar proxy container named 'istio-proxy' alongside the app container in each pod.

2. Step 2: Interpret pod container count

   If pods show two containers including 'istio-proxy', injection worked. One container means no injection. CrashLoopBackOff or no pods indicate errors or missing pods.

3. Final Answer:

   Pods show two containers: one for the app and one named 'istio-proxy' -> Option A

4. Quick Check:

   Sidecar proxy container present = B [OK]

Hint: Look for 'istio-proxy' container in pods [OK]

Common Mistakes:

• Expecting only one container per pod
• Ignoring pod status errors
• Confusing missing pods with injection failure

4. You applied Istio sidecar injection label to a namespace but pods still lack the 'istio-proxy' container. What is the likely cause?

medium

A. Namespace label was added after pods were created; pods need restart

B. Istio is not installed on the cluster

C. Pods are running on nodes without Istio installed

D. The label key was misspelled as 'istio-injectiong'

Solution

1. Step 1: Understand sidecar injection timing

   Istio injects sidecars when pods are created. Adding the label after pods exist does not inject sidecars automatically.

2. Step 2: Consider pod lifecycle

   Pods must be restarted or recreated after labeling the namespace to get sidecars injected.

3. Final Answer:

   Namespace label was added after pods were created; pods need restart -> Option A

4. Quick Check:

   Pods need restart after labeling = A [OK]

Hint: Restart pods after adding injection label to namespace [OK]

Common Mistakes:

• Assuming label applies instantly to existing pods
• Ignoring pod restart requirement
• Confusing label typos with installation issues

5. How does Istio improve security between microservices without changing application code?

hard

A. By storing all secrets in a centralized database

B. By requiring developers to add encryption code in each service

C. By blocking all external traffic to microservices

D. By injecting sidecar proxies that handle mutual TLS encryption automatically

Solution

1. Step 1: Identify Istio's security method

   Istio injects sidecar proxies that transparently encrypt traffic between services using mutual TLS without code changes.

2. Step 2: Eliminate incorrect options

   Developers do not need to add encryption code. Istio does not store secrets in a database nor block all external traffic.

3. Final Answer:

   By injecting sidecar proxies that handle mutual TLS encryption automatically -> Option D

4. Quick Check:

   Istio uses sidecars for automatic encryption = C [OK]

Hint: Istio sidecars add encryption without code changes [OK]

Common Mistakes:

• Thinking developers must add encryption code
• Confusing Istio with secret storage
• Assuming Istio blocks all external traffic