Istio
Istio is an open-source service mesh for Kubernetes. It puts proxies in the path of service-to-service traffic so the platform can enforce mutual TLS (mTLS), apply access policies, route requests and collect metrics, without changes to application code. The control plane, istiod, pushes configuration and certificates to those proxies.
How it works
Istio has two data-plane modes. In sidecar mode, every pod gets an Envoy proxy container. In ambient mode, a shared ztunnel on each node handles layer 4: mTLS, identity and connection-level policy. Optional waypoint proxies add layer 7 features such as header-based routing and retries only for the services that need them.
For example, 200 pods on 3 nodes means 200 sidecars in sidecar mode, but only 3 ztunnels in ambient mode. A policy such as "only the payments service may call the ledger" then holds even on a flat network where every pod can reach every other pod.
Why it matters in production
A mesh is a security and reliability control, so it needs the same care as any production dependency: upgrade istiod and proxies in a tested order, watch certificate rotation, and know which features need a waypoint before you depend on them.
See also
On the One2N blog
References
