Service mesh concept overview in Kubernetes - Commands & Configuration

Introduction

When you run many small services that need to talk to each other, it can get hard to manage how they connect, secure their communication, and watch their traffic. A service mesh helps by adding a layer that handles these tasks automatically, so your services can focus on their work without worrying about networking details.

When you have multiple microservices that need secure and reliable communication.

When you want to monitor and control traffic between services without changing their code.

When you need automatic retries, load balancing, or circuit breaking between services.

When you want to enforce security policies like encryption and authentication between services.

When you want to collect detailed metrics and logs about service-to-service communication.

Commands

Create a separate namespace to install the service mesh components safely isolated from your app workloads.

Terminal

kubectl create namespace istio-system

Expected Output

namespace/istio-system created

Install the minimal Istio operator which manages the service mesh installation and lifecycle.

Terminal

kubectl apply -f https://github.com/istio/istio/releases/download/1.18.0/istio-minimal-operator.yaml -n istio-system

Expected Output

customresourcedefinition.apiextensions.k8s.io/istiooperators.install.istio.io created

customresourcedefinition.apiextensions.k8s.io/istiooperatorconfigs.install.istio.io created

serviceaccount/istio-operator created

clusterrole.rbac.authorization.k8s.io/istio-operator created

clusterrolebinding.rbac.authorization.k8s.io/istio-operator created

deployment.apps/istio-operator created

Apply a simple IstioOperator custom resource to install the minimal service mesh control plane in the cluster.

Terminal

kubectl apply -f - <<EOF
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
  namespace: istio-system
  name: example-istiocontrolplane
spec:
  profile: minimal
EOF

Expected Output

istiocontrolplane.install.istio.io/example-istiocontrolplane created

Check that the service mesh control plane pods are running and ready.

Terminal

kubectl get pods -n istio-system

Expected Output

NAME                                   READY   STATUS    RESTARTS   AGE

istio-operator-7d9f9f9f9f-abcde       1/1     Running   0          1m

istiod-6f7d8f9f9f-xyz12                1/1     Running   0          30s

Key Concept

If you remember nothing else from this pattern, remember: a service mesh transparently manages how your services connect, secure, and observe each other without changing their code.

Common Mistakes

Trying to install the service mesh components in the default namespace.

This can cause conflicts with existing workloads and makes management harder.

Always create and use a dedicated namespace like 'istio-system' for service mesh components.

Not verifying that the control plane pods are running after installation.

If the control plane is not running, the service mesh features won't work and troubleshooting becomes difficult.

Run 'kubectl get pods -n istio-system' to confirm all pods are ready before proceeding.

Applying incomplete or incorrect IstioOperator configuration files.

This can cause installation failures or partial setups that don't provide full service mesh functionality.

Use official minimal or default profiles from Istio documentation and validate YAML syntax before applying.

Summary

Create a dedicated namespace for service mesh components to keep them isolated.

Install the service mesh control plane using official operator manifests and configuration.

Verify the control plane pods are running to ensure the mesh is ready for use.

Practice

1. What is the main purpose of a service mesh in Kubernetes?

easy

A. To manage communication between services securely and reliably

B. To store data persistently for applications

C. To schedule pods on nodes

D. To build container images automatically

Solution

1. Step 1: Understand service mesh role

   A service mesh manages how services communicate with each other, focusing on security and reliability.

2. Step 2: Compare options

   Options B, C, and D relate to storage, scheduling, and building images, which are not service mesh functions.

3. Final Answer:

   To manage communication between services securely and reliably -> Option A

4. Quick Check:

   Service mesh = secure, reliable service communication [OK]

Hint: Service mesh controls service communication, not storage or scheduling [OK]

Common Mistakes:

• Confusing service mesh with storage or scheduling tools
• Thinking service mesh builds container images
• Assuming service mesh replaces Kubernetes itself

2. Which component is typically deployed alongside an application pod to enable a service mesh?

easy

A. A sidecar proxy

B. A persistent volume

C. A Kubernetes scheduler

D. A container registry

Solution

1. Step 1: Identify service mesh architecture

   Service meshes use sidecar proxies deployed with app pods to intercept and manage traffic.

2. Step 2: Eliminate unrelated components

   Persistent volumes store data, schedulers assign pods to nodes, and container registries store images, none manage traffic.

3. Final Answer:

   A sidecar proxy -> Option A

4. Quick Check:

   Sidecar proxy = service mesh traffic manager [OK]

Hint: Sidecar proxies run with pods to manage traffic [OK]

Common Mistakes:

• Confusing sidecar proxy with storage or scheduling components
• Thinking service mesh requires changes inside app code
• Assuming container registry is part of service mesh

3. Given a Kubernetes cluster with a service mesh installed, what happens when one service calls another?

medium

A. The call is converted into a database query

B. The call bypasses the sidecar and goes directly to the service

C. The service mesh blocks all calls by default

D. The call is routed through the sidecar proxy which handles retries and security

Solution

1. Step 1: Understand service mesh traffic flow

   Service mesh sidecars intercept calls between services to add features like retries and security.

2. Step 2: Evaluate options

   The call bypasses the sidecar and goes directly to the service is incorrect because calls do not bypass sidecars. The service mesh blocks all calls by default is wrong; calls are allowed with policies. The call is converted into a database query is unrelated.

3. Final Answer:

   The call is routed through the sidecar proxy which handles retries and security -> Option D

4. Quick Check:

   Service calls go through sidecar proxy [OK]

Hint: Service mesh sidecar proxies manage calls with retries and security [OK]

Common Mistakes:

• Assuming calls bypass the service mesh
• Thinking service mesh blocks all traffic
• Confusing service calls with database queries

4. You deployed a service mesh but notice that traffic between services is not being intercepted. What is a likely cause?

medium

A. The pods have no CPU resources assigned

B. The sidecar proxy was not injected into the pods

C. The container images are missing

D. The Kubernetes API server is down

Solution

1. Step 1: Identify why traffic is not intercepted

   Service mesh requires sidecar proxies injected into pods to intercept traffic.

2. Step 2: Rule out unrelated issues

   Kubernetes API server down or missing images cause broader failures, not just traffic interception. CPU limits affect performance but not injection.

3. Final Answer:

   The sidecar proxy was not injected into the pods -> Option B

4. Quick Check:

   Missing sidecar = no traffic interception [OK]

Hint: Check if sidecar proxy is injected in pods [OK]

Common Mistakes:

• Blaming Kubernetes API server for traffic interception issues
• Ignoring sidecar injection step
• Assuming CPU limits block traffic interception

5. You want to add fine-grained traffic control between services in your Kubernetes cluster. How does a service mesh help achieve this?

hard

A. By replacing Kubernetes networking with a custom network plugin

B. By modifying the application source code to handle traffic rules

C. By using sidecar proxies to route, split, and secure traffic without changing app code

D. By storing traffic rules in a database external to the cluster

Solution

1. Step 1: Understand service mesh traffic control features

   Service meshes use sidecar proxies to manage traffic routing, splitting, and security transparently.

2. Step 2: Evaluate other options

   By modifying the application source code to handle traffic rules requires app code changes, which service mesh avoids. By replacing Kubernetes networking with a custom network plugin is about networking plugins, not service mesh. By storing traffic rules in a database external to the cluster is unrelated to traffic control mechanisms.

3. Final Answer:

   By using sidecar proxies to route, split, and secure traffic without changing app code -> Option C

4. Quick Check:

   Sidecar proxies enable traffic control without app changes [OK]

Hint: Service mesh controls traffic via sidecars, no app code changes needed [OK]

Common Mistakes:

• Thinking app code must be changed for traffic control
• Confusing service mesh with network plugins
• Assuming traffic rules are stored externally