Kubernetes - Service Mesh
You want to monitor traffic between services using Linkerd but want minimal resource use. Which approach fits best?
You want to monitor traffic between services using Linkerd but want minimal resource use. Which approach fits best?
hard📝 Workflow Q8 of 15
Step-by-Step Solution
Solution:
Step 1: Identify monitoring options in Linkerd
Linkerd provides lightweight telemetry integrated with Prometheus for metrics.Step 2: Evaluate resource use
Using built-in telemetry is efficient compared to adding heavy meshes or manual logging.Final Answer:
Use Linkerd's built-in lightweight telemetry with Prometheus -> Option AQuick Check:
Lightweight telemetry + Prometheus = C [OK]
Quick Trick: Linkerd telemetry is lightweight and Prometheus-friendly [OK]
Common Mistakes:
- Adding Istio increases resource use
- Manual logging is complex and heavy
- Disabling proxies stops monitoring
Master "Service Mesh" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes