Overview
What this challenge is about.
Phase 1: install Istio alongside Linkerd in PERMISSIVE mode (Istio sidecars injected, Linkerd proxies remain). Phase 2: migrate non-critical namespaces first (4 namespaces) by relabeling pods and rolling them — both meshes inspect traffic, only Istio's policy is enforced. Phase 3: migrate critical namespaces (3) after policy parity is proven. Phase 4: uninstall Linkerd. Automate cutover with a Helm chart + an Argo Rollout per service. Validate latency parity (p99 within 5 percent) at every phase. Deliver migration plan, automation code, validation report, and 7-page postmortem.
The Brief
What you'll do, and what you'll demonstrate.
Migrate from Linkerd to Istio across 7 clusters and 24 namespaces with no latency regression and zero customer-visible downtime.
Earning criteria — what you'll demonstrate
- Plan a service-mesh migration with both meshes coexisting safely
- Compare Linkerd's micro-proxy model to Istio's Envoy-based data plane
- Automate per-namespace cutover with Helm + progressive delivery
- Validate mesh-migration latency parity at p99 across multiple clusters
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.