Kubernetes - Service Mesh
You notice that your Envoy sidecar proxy is not forwarding traffic correctly. Which of the following is the most likely cause?
You notice that your Envoy sidecar proxy is not forwarding traffic correctly. Which of the following is the most likely cause?
medium📝 Troubleshoot Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Analyze Envoy sidecar traffic issues
Envoy needs proper network permissions (like NET_ADMIN) to intercept and forward traffic.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.Final Answer:
The Envoy container is missing required network permissions or capabilities. -> Option CQuick Check:
Envoy needs network permissions to forward traffic [OK]
Quick Trick: 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
Master "Service Mesh" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes