Linkerd overview in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Linkerd in the context of microservices?

Linkerd is a service mesh that helps manage communication between microservices by providing features like load balancing, security, and observability without changing application code.

intermediate

How does Linkerd improve security between microservices?

Linkerd encrypts communication between services using mutual TLS (mTLS), ensuring data is secure and trusted without needing changes in the application.

intermediate

What role do proxies play in Linkerd's architecture?

Linkerd uses lightweight proxies deployed alongside each microservice instance to intercept and manage all network traffic, enabling features like retries, timeouts, and metrics collection.

beginner

Name two key observability features provided by Linkerd.

Linkerd provides detailed metrics and distributed tracing to help monitor service health and diagnose issues in microservice communication.

intermediate

Why is Linkerd considered lightweight compared to other service meshes?

Linkerd is designed to be simple and efficient, using minimal resources and easy installation, making it suitable for small to large scale microservice environments.

What primary problem does Linkerd solve in microservices?

A Manages communication between microservices

B Stores data for microservices

C Builds user interfaces

D Manages databases

Linkerd manages communication between microservices by providing features like load balancing and security.

Which security feature does Linkerd use to encrypt service communication?

A Mutual TLS (mTLS)

B OAuth

C API keys

D Firewall

Linkerd uses mutual TLS (mTLS) to encrypt and authenticate communication between services.

Where are Linkerd proxies deployed in a microservices environment?

A On a central server

B Inside the database

C Alongside each microservice instance

D Only on the client side

Linkerd deploys lightweight proxies next to each microservice instance to intercept traffic.

Which of the following is NOT a feature provided by Linkerd?

A Load balancing

B Distributed tracing

C Automatic retries

D User authentication UI

Linkerd does not provide user interface features like authentication UI; it focuses on service communication.

Why might a team choose Linkerd over other service meshes?

A Because it requires heavy resource usage

B Because it is lightweight and easy to install

C Because it replaces databases

D Because it builds mobile apps

Linkerd is known for being lightweight and simple to install, making it attractive for many teams.

Explain how Linkerd enhances security and reliability in microservice communication.

Think about how Linkerd protects data and handles failures between services.

Describe the architecture of Linkerd and how it manages traffic between microservices.

Consider the roles of proxies and control plane in Linkerd.

Practice

1. What is the primary purpose of Linkerd in a microservices architecture?

easy

A. To write business logic for microservices

B. To replace the database layer in microservices

C. To help microservices communicate securely and reliably

D. To serve as a frontend framework for microservices

Solution

1. Step 1: Understand Linkerd's role

   Linkerd is a service mesh designed to manage communication between microservices.

2. Step 2: Identify its main function

   It ensures secure and reliable communication without changing service code.

3. Final Answer:

   To help microservices communicate securely and reliably -> Option C

4. Quick Check:

   Linkerd = Secure, reliable microservice communication [OK]

Hint: Linkerd manages communication, not business logic or UI [OK]

Common Mistakes:

• Confusing Linkerd with database or frontend tools
• Thinking Linkerd writes application code
• Assuming Linkerd replaces microservices

2. Which of the following commands is used to check the health of Linkerd after installation?

easy

A. linkerd check

B. linkerd install

C. linkerd monitor

D. linkerd deploy

Solution

1. Step 1: Recall Linkerd CLI commands

   Linkerd provides commands like install, check, and monitor for managing the service mesh.

2. Step 2: Identify the health check command

   The linkerd check command verifies if Linkerd is installed and running correctly.

3. Final Answer:

   linkerd check -> Option A

4. Quick Check:

   Health check = linkerd check [OK]

Hint: Use 'linkerd check' to verify installation health [OK]

Common Mistakes:

• Using 'linkerd install' to check health
• Confusing 'linkerd monitor' with health check
• Assuming 'linkerd deploy' is a valid command

3. Given the following snippet, what will linkerd check report if Linkerd proxies are not injected into the services?

kubectl get pods
NAME                     READY   STATUS    RESTARTS   AGE
service-a-12345           1/1     Running   0          10m
service-b-67890           1/1     Running   0          10m

medium

A. Info: Services are running but no Linkerd installed

B. All checks pass, Linkerd is fully operational

C. Error: Kubernetes cluster not reachable

D. Warning: No proxies detected, Linkerd not fully enabled

Solution

1. Step 1: Understand proxy injection role

   Linkerd requires proxies injected into pods to manage traffic and security.

2. Step 2: Analyze pod readiness and proxy presence

   Pods show 1/1 ready, but no proxy sidecar means Linkerd features are not active.

3. Final Answer:

   Warning: No proxies detected, Linkerd not fully enabled -> Option D

4. Quick Check:

   No proxies = Warning from linkerd check [OK]

Hint: No proxies means Linkerd features inactive, expect warnings [OK]

Common Mistakes:

• Assuming pods ready means Linkerd is fully working
• Confusing cluster reachability errors with proxy injection
• Thinking Linkerd works without proxies

4. You deployed Linkerd but notice that traffic is not being routed through the proxies. Which of the following is the most likely cause?

medium

A. Proxies were not injected into the service pods

B. The services are not exposing any ports

C. The Kubernetes cluster is down

D. The Linkerd control plane is not installed

Solution

1. Step 1: Check Linkerd traffic routing requirements

   Traffic routing requires proxies injected into pods to intercept and manage requests.

2. Step 2: Identify common deployment mistakes

   If proxies are missing, traffic bypasses Linkerd, causing routing issues.

3. Final Answer:

   Proxies were not injected into the service pods -> Option A

4. Quick Check:

   Missing proxies = traffic not routed [OK]

Hint: Missing proxies cause traffic routing failure [OK]

Common Mistakes:

• Assuming control plane absence causes routing issues
• Blaming Kubernetes cluster status without checking proxies
• Ignoring service port exposure as a cause

5. You want to add observability to your microservices using Linkerd. Which combination of features does Linkerd provide to achieve this without changing your service code?

hard

A. Database management, caching, and load balancing

B. Traffic routing, security, and built-in monitoring dashboards

C. Frontend UI components, API gateways, and authentication

D. Code instrumentation, manual tracing, and custom logging

Solution

1. Step 1: Identify Linkerd's observability features

   Linkerd provides traffic routing, security, and monitoring dashboards automatically via proxies.

2. Step 2: Exclude unrelated features

   Database, frontend UI, and manual code changes are outside Linkerd's scope.

3. Final Answer:

   Traffic routing, security, and built-in monitoring dashboards -> Option B

4. Quick Check:

   Linkerd = routing + security + monitoring [OK]

Hint: Linkerd adds observability without code changes [OK]

Common Mistakes:

• Confusing Linkerd with database or frontend tools
• Thinking manual code changes are needed for observability
• Mixing Linkerd with unrelated infrastructure components