Argo CD vs Istio

Argo CD is open source and free to use. No licensing fees, subscription charges, or commercial restrictions apply. The project is maintained by the CNCF community.

Only if you have enough services, or a compliance requirement, that implementing mTLS, retries and tracing per language has become unmanageable. Below roughly a few dozen services, an ingress controller plus good client libraries usually delivers more reliability for less operational cost.

Argo CD checks Git and Helm repositories every 3 minutes by default to detect configuration changes, enabling timely deployment of updates.

Ambient removes the per-pod proxy and its startup ordering problems and costs less at high pod counts, but it is a newer architecture and does not cover every sidecar feature. New deployments should evaluate ambient first; existing sidecar meshes should treat the move as a migration project.

Linkerd is deliberately smaller, uses its own Rust proxy rather than Envoy, and is quicker to operate; Istio has a far larger feature surface, multi-cluster and VM support, and broader vendor backing. Note that Linkerd's stable distribution builds are commercially licensed by Buoyant, whereas Istio's releases are freely available.

Solo.io and Tetrate sell supported distributions and control planes, and Google offers Cloud Service Mesh as a managed option. The upstream project itself is CNCF-governed with community support.

Partly. Virtual machine workloads can be added to a mesh, but the tooling, documentation and community experience are heavily Kubernetes-centred, so a VM-majority estate is fighting the grain of the project.