Why Linkerd doesn’t use Envoy

Why Linkerd doesn’t use Envoy

  • December 4, 2020
Table of Contents

Why Linkerd doesn’t use Envoy

Why Linkerd doesn’t use Envoy In this article I’m going to describe why Linkerd isn’t built on Envoy. This is a bit of a weird article to write.

After all, there are a million projects that Linkerd doesn’t use, and none of those decisions deserve a blog post. But the fact that Linkerd doesn’t use Envoy specifically has become a common enough topic of discussion that it probably deserves a good explanation. Let me also state upfront that this is not an “Envoy sucks” blog post.

Envoy is a great project, is clearly a popular choice for many, and we have nothing but respect for the fine folks who work on it. We recommend Envoy to Linkerd users every day in the form of ingress controllers like Ambassador, and there are production systems around the world today where you can find Envoy and Linkerd working side by side.

Source: linkerd.io

Share :
comments powered by Disqus

Related Posts

B-21 stealth bomber running Kubernetes for better SDLC experience

B-21 stealth bomber running Kubernetes for better SDLC experience

The new stealth U.S. Air Force B-21 bomber has taken yet another key technological step toward being ready for war, through integrated computer automation designed to streamline information, improve targeting and offer pilots organized warzone information in real-time. Air Force and Northrop Grumman developers recently completedan essential software-empowered process intended to bring greater levels of information processing, data management and new measures of computerized autonomy,according to published statements from Air Force Acquisition Executive Dr. William Roper. Through virtualization and software-hardware synergy, B-21 sensors, computers and electronics can better scale, deploy and streamline procedural functions such as checking avionics specifics, measuring altitude and speed and integrating otherwise disparate pools sensor information.

Read More