The situation
The SaaS (sells observability to engineering teams, eats its own dogfood) needs Istio's AuthorizationPolicy to ship per-tenant network isolation — a top customer demand from the Enterprise tier.
Your task
Migrate from Linkerd to Istio across 7 clusters and 24 namespaces with no latency regression and zero customer-visible downtime.
The brief
What you do
- 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.
You deliver
Migration plan, automation code, validation report, and 7-page postmortem.
What you will practice
- 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
A suggested way in
- Both-meshes-coexist requires careful exclusion lists so traffic isn't double-proxied; this is the most common bug
- Migrate the noisy-namespace first to surface chaos, save critical namespaces for the end
- p99 latency parity beats p50 — sidecar overhead bites in the tail, not the median
Skills you will practice
Istio, Linkerd, Service mesh, Kubernetes, Multi cluster, Migration strategy
How it is assessed
- Migration plan25%
Four phases with explicit go/no-go gates per namespace.
- Automation quality30%
Helm + Argo Rollouts make cutover idempotent and reversible.
- Validation rigor25%
Latency parity within 5 percent at p99 reported per namespace per phase.
- Postmortem honesty20%
What-didn't-work section is concrete and gives the next team a head start.
Resources
- IstioTool
Target service mesh with rich AuthorizationPolicy support.
- LinkerdTool
Source service mesh; needs clean uninstall after migration.
- HelmTool
Automation chart for per-namespace cutover.
- Argo RolloutsTool
Progressive delivery for safe service migration.
- PrometheusTool
Latency parity measurement across both meshes.
- GrafanaTool
Per-namespace migration dashboards.
- NotionTool
Migration plan and postmortem authoring.
Finish it. Earn this.
A verified certificate with your name. Anyone can check it.
Time to practice.
Solve this challengeMore like this.
- Software EngineerBuild a Multi-Level Feedback Queue Scheduler in xv6
- Software EngineerReverse-Engineer a Stripped Binary to Restore Linking Symbols
- Software EngineerImplement a Distance-Vector Routing Algorithm
- AI EngineerEnd-to-End Lane Following on a Donkeycar Platform
-
Build a Multi-Level Feedback Queue Scheduler in xv6 Software Engineer Fork the xv6-riscv repository and implement MLFQ in proc.c with 3 priority queues, per-queue time slices (10ms / 20ms / 40ms), priority demotion on sl operating systemsschedulingc programming Open challenge → -
Reverse-Engineer a Stripped Binary to Restore Linking Symbols Software Engineer Receive the stripped shared object (Linux ELF, x86-64, ~280KB), a crash dump with 12 frames of indecipherable addresses, and 4 years of partial git hi reverse engineeringlinking and loadingmachine code Open challenge → -
Implement a Distance-Vector Routing Algorithm Software Engineer Implement distance-vector routing in Python: each simulated router maintains a distance vector, exchanges vectors with neighbors every 1 second of sim routingdistance vectornetwork simulation Open challenge → -
End-to-End Lane Following on a Donkeycar Platform AI Engineer Use the public Donkeycar Tub dataset (or collect about 30 minutes of driving on the simulator). Train a CNN-policy baseline (the Donkeycar default arc end to end learningimitation learningpytorch Open challenge →