Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hands on with Linkerd 2.0

kubernetes.io

Post reply on HN
Print view View original

31–39 of 39 posts

Re: Hands on with Linkerd 2.0

#31

Post by stock_toaster »

fosk wrote: post #18
stock_toaster wrote: post #15

Doesn't seem like it is designed to work outside of k8s anymore? Anyone know of a service mesh that is intended to run in a more standalone fashion? (itsio also integrates very strongly to k8s)

Marco, CTO of Kong here. This is exactly what Kong has been doing for a while and with the newly announced Kong 1.0 release [1] (2 days ago) we also support Service Mesh with a lightweight runtime that has been running in production since 3.5 years across multiple platforms, hybrid container orchestration platforms and even hybrid baremetal/cloud deployments. GA for Kong 1.0 will include Service Mesh (we have RC1 now…

Thanks, I’ll certainly take a look!

Re: Hands on with Linkerd 2.0

#32

Post by lhopki01 »

SushiMon wrote: post #7
eikenberry wrote: post #3

Earlier quoted context omitted.

There was a blog post just a few days ago comparing them (along with Linkerd and Consul Connect). Maybe it will help. https://kubedex.com/istio-vs-linkerd-vs-linkerd2-vs-consul/

The post is long but it was really written from the POV of an infrastructure owner (DevOps) and not from the POV of a service owner/developer which is actually the target for Linkerd 2.0. FWIW - the post says it takes 5 mins to install Istio. I find that very, very hard to believe.

It took me about 5 minutes and then a few more hours tweaking rules to match what our existing services needed.

Re: Hands on with Linkerd 2.0

#33

Post by otterley »

williamallthing wrote: post #29
jazoom wrote: post #13

Earlier quoted context omitted.

A JVM attached as a sidecar to each pod is a waste of resources. Garbage collection isn't great for a high performance proxy.

Exactly! We considered Go briefly but in the end, the magic intersection of native-code performance, plus guaranteed memory safety, trumped every other concern for the data plane.

Is there a significant demonstrable performance difference between Linkerd 2 and Envoy as a result?

Re: Hands on with Linkerd 2.0

#34

Post by presspot »

brazzledazzle wrote: post #23
Thaxll wrote: post #20

I'm testing Istio at the moment and I feel those comments to be very inaccurate: "Traditional service meshes are an all-or-nothing proposition that add a significant layer of complexity to your stack. That’s not great." Istio is like k8 it's very modular and you setup what you need. "Traditional service meshes are designed to meet the needs of platform owners, and they dramatically underserve a more important audienc…

Are they talking about Istio? It seems way too new to call it “traditional”.

Buoyant invented the service mesh concept and added that term to our vernacular as a way to describe Linkerd 1.x and similar systems. Istio was built using the same pattern as Linkerd 1.0. Those are "traditional", albeit in internet years not real years.

Linkerd 2.0 takes a fundamentally different approach. It's tiny, fast, lightweight and designed to add value as a service sidecar (installed on a single service) without any "mesh". If multiple service owners install Linkerd 2.0, it self-morphs into a mesh configuration and provides all of the value of a service mesh. This creates an installation and deployment pattern that is very practical and bottoms-up, delivering value to the individual service (and service owner) but also supporting a higher-level abstraction of a mesh at the platform level. This is a fundamental innovation and, hence, a new model for service mesh patterns versus the original, er, traditional model.

Re: Hands on with Linkerd 2.0

#35

Post by presspot »

barbecue_sauce wrote: post #24
brazzledazzle wrote: post #23

Earlier quoted context omitted.

Are they talking about Istio? It seems way too new to call it “traditional”.

What would be an example of a "traditional" service mesh then?

Linkerd 1.0 and Istio are traditional service meshes; you install them in their totality across an entire platform. They are rich in features and bulky, completely overkill for a single service.

Linkerd 2.0 follows a new bottoms-up model that is, frankly, non-traditional. An individual service owner can install a lightweight package on a single service and derive immediate value. When multiple service owners on a project adopt Linkerd 2.0, their services will properly "mesh" without any platform-level installs. This makes adoption organic and immediately valuable for a single dev but also for an entire project as it gets installed into more services. Game changing IMHO.

Re: Hands on with Linkerd 2.0

#37

Post by clux »

jazoom wrote: post #14

This looks great but I'll hold off using it until it gets automatic sidecar injection. The CLI YAML-adulterer doesn't fit into my flow very well.

Honestly I'd much rather have some configurable yaml than some obscure app in the middle of your cluster that reads CRDs when what you're doing is just adding a side car.

At least this way you can tell if your local yaml is applied or not without a complicated diffing algorithm that compensates for an in-cluster modifier.

Re: Hands on with Linkerd 2.0

#38

Post by jazoom »

clux wrote: post #37
jazoom wrote: post #14

This looks great but I'll hold off using it until it gets automatic sidecar injection. The CLI YAML-adulterer doesn't fit into my flow very well.

Honestly I'd much rather have some configurable yaml than some obscure app in the middle of your cluster that reads CRDs when what you're doing is just adding a side car. At least this way you can tell if your local yaml is applied or not without a complicated diffing algorithm that compensates for an in-cluster modifier.

I would too, except, have you seen what your YAML looks like after all the Linkerd additions? There's a reason they don't even mention in the docs exactly what it changes.

Re: Hands on with Linkerd 2.0

#39

Post by williamallthing »

stock_toaster wrote: post #30
williamallthing wrote: post #21

Earlier quoted context omitted.

Just a question of starting point. Linkerd 1.x has been running for years on multiple platforms, and we'll get there with the 2.x line as well.

Ah. The docs read like k8s was the only concern. I’ll keep an eye on it for possible future day where it supports bare OS.

You can start with Linkerd 1.x today. Supports pretty much every platform. :)
Post reply on HN