Linkerd Reviews & Product Details

Lightweight and resource-efficient, ideal for Kubernetes.

Automatic mTLS encryption for secure service communication.

Instant observability with golden metrics, no extra setup needed.

Built-in reliability with automatic retries and timeouts.

Kubernetes-native, seamlessly integrated for easy operation. Review collected by and hosted on G2.com.

Limited Customization: Linkerd keeps things simple, but that also means fewer advanced options for customizing traffic management compared to some other service meshes.

Missing Some Power Features: It doesn’t have all the fancy features like traffic shadowing or complex routing rules that you might find in heavier meshes like Istio.

Kubernetes Only: Linkerd is designed purely for Kubernetes, so if you’re running on other platforms or need multi-cloud support, it might not cover all your needs.

Smaller Ecosystem: While Linkerd has a great community, it doesn’t have the vast ecosystem and range of plugins you’ll find with bigger meshes like Istio. Review collected by and hosted on G2.com.

It is a lightweightand easy to set up, which works good with kubernetes without slowing things down. It has a security built-in and shows a problem very fast, and it makes easy to manage and fix stuff. Review collected by and hosted on G2.com.

It can be limited in features compared to other service meshes. Also it will be difficult for beginners who are new to kubernetes and service meshes. Review collected by and hosted on G2.com.

The ease of setting up and simplicity of the tech stack. It's feature to enable service mirroring in order to provide cross cluster service communication and building the service mesh around the cluster components is a deal breaker. Review collected by and hosted on G2.com.

Till version 2.5 it was open source and now it is anounced to be a licensed one. Review collected by and hosted on G2.com.

I like how easy it is to install and especially that it is a very light weight service mesh. Compared to other solutions in the industry , it is the most lightweight and have one of the best documentation available Review collected by and hosted on G2.com.

I don't particularly dislike anything about it. I have loved working with linkerd and havnt disliked anything. One think is that it sometimes doesn't install for me and i have to reinstall it to work. Review collected by and hosted on G2.com.

In the majority of cases, Linkerd can be used with very minimal configuration and provide benefits to a Kubernetes hosted application stack. Some of the best features include elements such as highly effective weighted load-balancing for HTTP and GRPC traffic, and the ability to use security policies to limit which pods can talk to other pods in order to lock down the internals of your cluster. The proxies are very low overhead, especially if you're comparing to an envoy/istio based environment, and having a barely-there footprint means there little to no cost to deploying into most clusters. Review collected by and hosted on G2.com.

The multi-cluster experience doesn't handle a few of the scenarios we'd hope for, but this is something that's generally able to be worked around. Review collected by and hosted on G2.com.

Linkerd is dead simple to use.

It is also the fastest (added latency) and the lightest (resource consumption) service mesh.

It's great to see how much thought the maintainers put into ensuring "it just works" (especially across releases). Review collected by and hosted on G2.com.

It doesn't necessarily have all the features other service meshes have, but releases are frequent, and the community is super involved.

But I think most systems don't really need all of the features other service meshes offer. Review collected by and hosted on G2.com.

The zero-conf nature with an option to tap into enterprise features like using your own PKI. Also linkerd is super stable and robust and offers great performance Review collected by and hosted on G2.com.

Honestly, can't think of anything major. Review collected by and hosted on G2.com.

The system is essentially zero-config for dynamic services and namespaces Review collected by and hosted on G2.com.

The pods seem to get into a split brain state very frequently, and we have to perform a rolling restart to bring back stability. It is bad enough now that we have a job perform the restart nightly Review collected by and hosted on G2.com.