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.
Hands on with Linkerd 2.0
11–20 of 39 posts
Re: Hands on with Linkerd 2.0
#12For those that care, the core of linkerd 2.0 is in Rust https://github.com/linkerd/linkerd2-proxy
Re: Hands on with Linkerd 2.0
#13Re: Hands on with Linkerd 2.0
#14The CLI YAML-adulterer doesn't fit into my flow very well.
Re: Hands on with Linkerd 2.0
#15Anyone know of a service mesh that is intended to run in a more standalone fashion? (itsio also integrates very strongly to k8s)
Re: Hands on with Linkerd 2.0
#16Re: Hands on with Linkerd 2.0
#17Earlier 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.
Re: Hands on with Linkerd 2.0
#18Doesn'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)
GA for Kong 1.0 will include Service Mesh (we have RC1 now, and RC2 coming soon).
Re: Hands on with Linkerd 2.0
#19For those that care, the core of linkerd 2.0 is in Rust https://github.com/linkerd/linkerd2-proxy
Re: Hands on with Linkerd 2.0
#20"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...