You want to migrate a Kubernetes app from a library-based approach to a service mesh. Which sequence of steps is correct?

hard📝 Workflow Q8 of 15

Kubernetes - Service Mesh

ARemove sidecar proxies, add communication library, redeploy app, test traffic

BDisable Kubernetes networking, add communication library, restart cluster

CLabel namespace for injection, deploy app without communication library, verify sidecars, test traffic

DDeploy app with both sidecar and communication library simultaneously

Step-by-Step Solution

Solution:

Step 1: Enable service mesh sidecar injection
Label the namespace to inject sidecar proxies automatically.
Step 2: Deploy app without the old communication library
Remove library-based code to avoid conflicts and rely on the mesh.
Step 3: Verify sidecars are running and test service traffic
Ensure sidecars are injected and communication works as expected.
Final Answer:
Label namespace for injection, deploy app without communication library, verify sidecars, test traffic -> Option C
Quick Check:
Migrate by enabling sidecar, removing library, verifying traffic [OK]

Quick Trick: Migrate by enabling sidecar injection and removing library code [OK]

Common Mistakes:

Master "Service Mesh" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Kubernetes Quizzes