Ewance
← All challenges Platform Engineer

Linkerd to Istio Migration for a Multi-Cluster Platform

Duration
4 weeks
Level
Expert
Type
Code
Team
1 to 5 people

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

  1. Phase 1: install Istio alongside Linkerd in PERMISSIVE mode (Istio sidecars injected, Linkerd proxies remain).
  2. 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.
  3. Phase 3: migrate critical namespaces (3) after policy parity is proven.
  4. Phase 4: uninstall Linkerd.
  5. Automate cutover with a Helm chart + an Argo Rollout per service.
  6. 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

  1. Both-meshes-coexist requires careful exclusion lists so traffic isn't double-proxied; this is the most common bug
  2. Migrate the noisy-namespace first to surface chaos, save critical namespaces for the end
  3. 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.

Sample Ewance certificate of completion, verified by LearnCoin
Sample certificate
Your proof

Finish it. Earn this.

A verified certificate with your name. Anyone can check it.

Time to practice.

Solve this challenge
Related challenges

More like this.