Start Without a Mesh

For a single cluster with one team and a handful of services, you can do without a mesh. NetworkPolicy, the Gateway API and cert-manager cover a lot, and there's nothing extra to upgrade. A mesh earns its place when many services across many teams need the same encryption, routing and telemetry without each one building it.

A service mesh promises mTLS, traffic shaping, observability, and policy without changing application code. It also adds a sidecar (or ambient proxy) per workload, more knobs than most teams need, and an upgrade surface that bites. By 2026 the choice is mature and clearer: use a mesh when you genuinely need its features, and skip it otherwise.

Questions worth answering first
  • You adopted Istio "for mTLS" and now spend Fridays debugging Envoy
  • You want canary deploys and don't know if Argo Rollouts or a mesh is the right layer
  • Compliance asked for "all pod-to-pod traffic encrypted" and you don't have an answer