Given a Kubernetes cluster with a service mesh installed, what happens when one service calls another?
medium📝 Command Output Q13 of 15
Kubernetes - Networking
Given a Kubernetes cluster with a service mesh installed, what happens when one service calls another?
AThe call is converted into a database query
BThe call bypasses the sidecar and goes directly to the service
CThe service mesh blocks all calls by default
DThe call is routed through the sidecar proxy which handles retries and security
Step-by-Step Solution
Solution:
Step 1: Understand service mesh traffic flow
Service mesh sidecars intercept calls between services to add features like retries and security.
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.
Final Answer:
The call is routed through the sidecar proxy which handles retries and security -> Option D
Quick Check:
Service calls go through sidecar proxy [OK]
Quick Trick: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
Master "Networking" in Kubernetes
9 interactive learning modes - each teaches the same concept differently