Kubernetes - Service MeshIf Envoy sidecar logs show no incoming requests but the app container is receiving traffic, what is the most probable reason?AEnvoy is crashing and unable to log requests.BTraffic is not being routed through Envoy due to missing iptables redirection rules.CThe app container is not actually receiving any traffic.DEnvoy is configured to log only outbound traffic.Check Answer
Step-by-Step SolutionSolution:Step 1: Confirm traffic flowIf app receives traffic but Envoy logs none, traffic likely bypasses Envoy.Step 2: Check iptables rulesEnvoy relies on iptables to redirect traffic; missing rules cause bypass.Final Answer:Traffic is not being routed through Envoy due to missing iptables redirection rules. -> Option BQuick Check:Missing iptables rules cause traffic to skip Envoy. [OK]Quick Trick: Missing iptables rules cause Envoy to miss incoming traffic. [OK]Common Mistakes:Assuming Envoy is crashing without evidenceIgnoring iptables role in traffic redirectionBelieving app container receives no traffic
Master "Service Mesh" in Kubernetes9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More Kubernetes Quizzes Helm Package Manager - Installing Helm - Quiz 5medium Helm Package Manager - Adding chart repositories - Quiz 15hard Monitoring and Logging - Kubernetes dashboard - Quiz 11easy Operators and Custom Resources - Why operators extend Kubernetes - Quiz 3easy Operators and Custom Resources - Why operators extend Kubernetes - Quiz 5medium Production Best Practices - Pod Disruption Budgets - Quiz 5medium Production Best Practices - Cluster upgrade strategies - Quiz 6medium Production Best Practices - Cluster upgrade strategies - Quiz 8hard Service Mesh - Mutual TLS for service communication - Quiz 2easy Troubleshooting - Why troubleshooting skills are critical - Quiz 1easy