Istio 1.18 vs Linkerd 2.14 for production K8s clusters

Has anyone migrated between Istio and Linkerd in production? We're running ~40 microservices on K8s 1.29 and currently using basic nginx ingress + manual service-to-service auth.

Our team is split:

• Istio camp wants full mTLS + traffic management features
• Linkerd camp prefers lightweight footprint (we're cost-conscious on Hetzner)

Key concerns:

• Resource overhead (CPU/memory)
• Learning curve for the team
• VirtualService/DestinationRule vs Linkerd's simpler policy model

Anyone have real-world production numbers? Latency impact? Would love to hear from teams that chose one over the other.

Linkerd's your answer for 40 services on Hetzner IMO. We did exactly this migration 18 months ago—Istio was eating ~8GB RAM just for the control plane, Linkerd sits at ~300-500MB. For mTLS + observability, Linkerd covers it without the CRD complexity. VirtualService/DestinationRule are powerful but overkill if you're not doing canary deployments or complex routing. That said, if traffic splitting or sophisticated retry policies matter to your roadmap, Istio pays for itself. Check https://istio.io/latest/docs/ for the feature matrix—honestly it'll show you Linkerd does 80% of what most teams need. Team friction point: Istio has bigger community, more StackOverflow answers. Linkerd docs are tighter though, less surface to learn.

Thanks lambda_dev, that's exactly the validation we needed—8GB vs 500MB is a huge difference on our Hetzner budget. Did you hit any rough patches during the actual migration, or was it pretty smooth with 40 services?

One thing I'd add: Linkerd's auto-mTLS is transparent, but Istio gives you way more granular control if you need policy exceptions later. On Hetzner with 40 services though, you'll probably never need that complexity. What matters more is whether your team can handle the Linkerd learning curve—it's genuinely smaller, but the mental model is different. I'd suggest a 2-week PoC on a staging cluster with realistic traffic patterns before deciding. Also check if any of your services use gRPC heavily; Linkerd handles that beautifully out of the box.