Live data from Hacker News

Hands on with Linkerd 2.0

kubernetes.io

11–20 of 39 posts

Re: Hands on with Linkerd 2.0

#11
post #9
post #7

Earlier quoted context omitted.

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.

For different definitions of "installed", I guess. I've been at an Istio workshop and it was less than 5 minutes to have it up and functional. Tweaking it obviously takes longer but that's true for every tool.

Right - meaning live configured Grafana dashboards, TLS up and running, etc - beyond just console stuff.

Re: Hands on with Linkerd 2.0

#13
post #4

For those that care, the core of linkerd 2.0 is in Rust https://github.com/linkerd/linkerd2-proxy

Do you know why they migrated from Scala?

A JVM attached as a sidecar to each pod is a waste of resources.

Garbage collection isn't great for a high performance proxy.

Re: Hands on with Linkerd 2.0

#17
post #9
post #7

Earlier quoted context omitted.

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.

For different definitions of "installed", I guess. I've been at an Istio workshop and it was less than 5 minutes to have it up and functional. Tweaking it obviously takes longer but that's true for every tool.

I’ve tried to install Istio on two clusters (at different points in time) and ran into blockers both times. YMMV.

Re: Hands on with Linkerd 2.0

#18

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, and RC2 coming soon).

[1] - https://konghq.com/blog/announcing-kong-1-0/

Re: Hands on with Linkerd 2.0

#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 audience: the service owners."

Not sure what it means, Istio is all about observability ect...

Post reply on HN