Re: [VOTE] linkerd moving to incubation

Brian Grant

At the moment, it looks like linkerd maybe still has more user mindshare, though envoy has more contributors.

Linkerd doesn't have to run as a host-level proxy, though I don't know how many people deploy it as a sidecar in practice. Host-level proxies also can make sense in some scenarios.

Maybe what you're getting at is what do we see as the driving use cases in the future for linkerd, relative to alternatives such as envoy and conduit? 

The only direct comparison I found in a quick search was in the envoy docs, and looks possibly out of date:

I don't know how much of an issue it is for linkerd users, but, irrespective of features and resource profiles, I could imagine a language preference, for dev and ops teams familiar with Java/Scala, particularly if they are writing plugins.

Since users will ask, it would be useful to provide some information they could use to choose one or the other.

But I don't think that impacts whether linkerd currently meets the bar for incubation or not, and by our "no kingmaking" principle it seems premature for us to choose one now.

On Thu, Mar 15, 2018 at 9:02 PM Justin Garrison <justinleegarrison@...> wrote:
​-1 non-binding

I think linkerd does a great job helping applications gain resilience from the network proxy and it has done an amazing 🙌 job and educating users and gaining production usage. I don't see linkerd as a product having as much traction going forward and have a hard time seeing more development diversity going forward. The resource requirements of it and the pattern of a hostcentric proxy have trade-offs that I don't think reinforce the other patterns and products the CNCF has promoted as cloud native.

Justin Garrison

On Thu, Mar 15, 2018 at 8:25 PM, Joseph Jacks <jacks.joe@...> wrote:
+1 (non-binding)

Join to automatically receive all group messages.