linkerd

Linkerd is a service mesh that adds observability, reliability, and security to Kubernetes applications without requiring code changes. It can monitor and report per-service success rates and latencies, automatically retry failed requests, and encrypt and validate connections between services.

Linkerd is designed to be fully transparent. You address other services just as you would without Linkerd, for example, service-name.namespace.svc.cluster.local, or service-name if within the same namespace.

No, Linkerd does not provide ingress itself. Instead, it works in conjunction with the ingress controller of your choice.

Linkerd's proxies are designed to continue operating even if they can't reach the control plane. They will use the latest service discovery information and fall back to DNS if asked to route to a service they don't have information for. However, new proxies deployed when the control plane is unreachable will not be able to operate until they can reach the control plane.

Linkerd uses multi-arch container images with support for x86, amd64, arm64, and arm.

Yes, enterprise distributions of Linkerd are available from Buoyant (the creators of Linkerd) as well as other companies.

Yes, commercial support for Linkerd is available from several companies. You can find a list of these companies on the Linkerd website.