Kubernetes - Service Mesh
You want to add observability and security features to your Kubernetes microservices without changing app code. Which approach is best and why?
You want to add observability and security features to your Kubernetes microservices without changing app code. Which approach is best and why?
hard📝 Best Practice Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Identify requirement to avoid app code changes
The question states no changes to app code are desired.Step 2: Match approach to requirement
Service mesh manages communication externally using sidecars, so it adds features without touching app code.Step 3: Evaluate other options
Library-based requires code changes; rewriting apps is costly; disabling features is not helpful.Final Answer:
Use a service mesh to manage features externally with sidecars -> Option CQuick Check:
No code change = service mesh best [OK]
Quick Trick: No code change? Choose service mesh [OK]
Common Mistakes:
- Choosing library-based despite no code change allowed
- Thinking rewriting apps is easier
- Ignoring observability and security needs
Master "Service Mesh" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes