Sidecar proxy concept (Envoy) in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary role of an Envoy sidecar proxy in Kubernetes?

In a Kubernetes pod, Envoy is often deployed as a sidecar proxy. What is its main function?

A To handle network traffic between microservices, providing features like load balancing and security.

B To store persistent data for the application running in the pod.

C To schedule pods across different nodes in the cluster.

D To monitor CPU and memory usage of the pod.

💡 Hint

Think about what a proxy does in networking and how Envoy fits into microservice communication.

Envoy acts as a network proxy that manages and controls traffic between microservices, enabling load balancing, security, and observability.

💻 Command Output

intermediate

Output of Envoy sidecar proxy logs in Kubernetes

You run kubectl logs -c envoy to check the Envoy sidecar logs. What kind of information will you most likely see?

A Kubernetes scheduler decisions and pod placement logs.

B Application business logic errors and stack traces.

C Details about incoming and outgoing HTTP requests, connection status, and errors.

D Database query results and cache hits.

💡 Hint

Envoy is a proxy; what kind of logs would a proxy generate?

Envoy logs show network traffic details such as HTTP requests, connection status, and any proxy-related errors.

❓ Configuration

advanced

Correct Envoy sidecar container configuration snippet in a Kubernetes pod spec

Which container spec snippet correctly configures Envoy as a sidecar proxy in a Kubernetes pod?

A

containers:
  - name: envoy
    image: envoyproxy/envoy:v1.22.0
    ports:
      - containerPort: 15001
    args: ["-c", "/etc/envoy/envoy.yaml"]

B

containers:
  - name: envoy
    image: envoyproxy/envoy
    ports:
      - containerPort: 8080
    command: ["/bin/bash"]

C

containers:
  - name: envoy
    image: envoyproxy/envoy:v1.22.0
    ports:
      - containerPort: 80
    args: ["--help"]

D

containers:
  - name: envoy
    image: envoyproxy/envoy:v1.22.0
    ports:
      - containerPort: 443
    args: ["-c", "/etc/envoy/config.yaml"]

💡 Hint

Look for the correct image tag, port, and config file argument.

Option A uses a specific Envoy version, the typical admin port 15001, and points to the standard config file path.

❓ Troubleshoot

advanced

Troubleshooting Envoy sidecar proxy failing to route traffic

You notice that traffic is not reaching your microservice through the Envoy sidecar proxy. Which of the following is the most likely cause?

A The pod's CPU limit is too low, causing Envoy to crash.

B Envoy configuration file has incorrect cluster or listener settings causing routing failure.

C Kubernetes node is out of disk space, preventing pod scheduling.

D The microservice container image tag is outdated.

💡 Hint

Think about what controls Envoy's routing behavior.

Envoy relies on its configuration file to route traffic correctly. Incorrect cluster or listener settings will cause routing failures.

🔀 Workflow

expert

Order the steps to deploy Envoy as a sidecar proxy in a Kubernetes pod

Arrange the following steps in the correct order to deploy Envoy as a sidecar proxy in a Kubernetes pod.

A 2,1,3,4

B 3,2,1,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Think about preparing config first, then pod spec, then deployment, then verification.

You first create the Envoy config, then add the sidecar container to the pod spec, deploy the pod, and finally verify the sidecar is working.

Practice

1. What is the main purpose of a sidecar proxy like Envoy in a Kubernetes pod?

easy

A. To manage network traffic for the application without changing its code

B. To replace the main application container

C. To store application data persistently

D. To run database services inside the pod

Solution

1. Step 1: Understand the role of sidecar proxies

   Sidecar proxies like Envoy run alongside the main app to handle network tasks such as routing, security, and monitoring.

2. Step 2: Identify what sidecars do not do

   They do not replace the app, store data, or run databases; they only assist with traffic management.

3. Final Answer:

   To manage network traffic for the application without changing its code -> Option A

4. Quick Check:

   Sidecar proxy = traffic manager [OK]

Hint: Sidecar proxies help apps with traffic, not replace them [OK]

Common Mistakes:

• Thinking sidecar replaces the app container
• Confusing sidecar with storage or database
• Assuming sidecar changes app code

2. Which of the following is the correct way to define a sidecar container for Envoy in a Kubernetes pod spec?

easy

A. containers: - name: app - image: envoyproxy/envoy

B. containers: - name: envoy - image: envoyproxy/envoy

C. containers: - name: envoy - image: nginx

D. containers: - name: envoyproxy - image: envoyproxy/envoy

Solution

1. Step 1: Identify the correct container name and image

   The sidecar container should be named clearly (e.g., 'envoy') and use the official Envoy image 'envoyproxy/envoy'.

2. Step 2: Check the options for correctness

   containers: - name: envoy - image: envoyproxy/envoy correctly names the container 'envoy' and uses the right image. containers: - name: app - image: envoyproxy/envoy misnames the container as 'app'. containers: - name: envoy - image: nginx uses the wrong image 'nginx'. containers: - name: envoyproxy - image: envoyproxy/envoy uses a different container name but correct image.

3. Final Answer:

   containers: - name: envoy - image: envoyproxy/envoy -> Option B

4. Quick Check:

   Envoy container name and image must match [OK]

Hint: Sidecar container name 'envoy' with image 'envoyproxy/envoy' [OK]

Common Mistakes:

• Using wrong container name for Envoy
• Using incorrect image like nginx
• Mixing app container with sidecar container

3. Given a pod with two containers: an app and an Envoy sidecar proxy, what happens when the app sends a request to an external service?

medium

A. The request goes directly from the app container to the external service without passing Envoy.

B. The request is duplicated and sent twice, once by the app and once by Envoy.

C. The request is blocked by Kubernetes and never leaves the pod.

D. The request is intercepted and routed through the Envoy sidecar proxy before reaching the external service.

Solution

1. Step 1: Understand Envoy's role as a sidecar proxy

   Envoy intercepts outbound requests from the app container to manage traffic, security, and monitoring.

2. Step 2: Trace the request flow

   The app's request is routed through Envoy before reaching the external service, enabling control and visibility.

3. Final Answer:

   The request is intercepted and routed through the Envoy sidecar proxy before reaching the external service. -> Option D

4. Quick Check:

   Envoy intercepts outbound traffic [OK]

Hint: Envoy sidecar intercepts app traffic to external services [OK]

Common Mistakes:

• Assuming app bypasses Envoy for external calls
• Thinking Kubernetes blocks outbound requests
• Believing requests are duplicated

4. You notice that your Envoy sidecar proxy is not forwarding traffic correctly. Which of the following is the most likely cause?

medium

A. The Kubernetes node is running out of CPU resources.

B. The app container image is outdated.

C. The Envoy container is missing required network permissions or capabilities.

D. The pod has only one container defined.

Solution

1. Step 1: Analyze Envoy sidecar traffic issues

   Envoy needs proper network permissions (like NET_ADMIN) to intercept and forward traffic.

2. Step 2: Evaluate other options

   App image version or node CPU issues may affect performance but not specifically Envoy forwarding. A pod with one container means no sidecar exists.

3. Final Answer:

   The Envoy container is missing required network permissions or capabilities. -> Option C

4. Quick Check:

   Envoy needs network permissions to forward traffic [OK]

Hint: Check Envoy network permissions if traffic not forwarded [OK]

Common Mistakes:

• Blaming app container image for Envoy issues
• Ignoring network capabilities needed by Envoy
• Assuming pod must have one container only

5. You want to add an Envoy sidecar proxy to an existing Kubernetes deployment without changing the app code. Which approach is best to achieve this?

hard

A. Modify the deployment YAML to add an Envoy container in the pod spec as a sidecar

B. Replace the app container image with one that includes Envoy inside

C. Create a separate pod running Envoy and route traffic through it externally

D. Add an init container that installs Envoy inside the app container at startup

Solution

1. Step 1: Understand sidecar pattern in Kubernetes

   Sidecars run as additional containers in the same pod, so modifying the pod spec to add Envoy is the standard way.

2. Step 2: Evaluate alternatives

   Replacing app image changes code, separate pods lose pod-local benefits, and init containers run before app start and can't run sidecars.

3. Final Answer:

   Modify the deployment YAML to add an Envoy container in the pod spec as a sidecar -> Option A

4. Quick Check:

   Add Envoy as sidecar container in pod spec [OK]

Hint: Add Envoy container to pod spec, no app code change needed [OK]

Common Mistakes:

• Replacing app image instead of adding sidecar
• Using separate pods losing sidecar benefits
• Misusing init containers for sidecar functionality