21–30 of 39 posts
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)
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.
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…
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”.
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?
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…
>> "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.
Istio is a very different beast from Linkerd. But out of curiosity, I just tried the latest Istio release on my laptop (1.0.2 on Docker for Mac K8s). The simplest configuration I found installs 50 (!) CRDs, 13 deployments, and is currently sitting at ~600mb of memory without any traffic. Perhaps by "modular" you mean you can add more modules on top of that?
(By contrast, Linkerd 2.0 installs 0 CRDs, 4 services, and is sitting at 250mb including 50mb full Grafana UI. It also does a lot less... but that's the point.)
That's the control plane. Let's not get started on the data plane.
>> "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...
This is all in the article. You can install Linkerd as a service owner on a single service. You'll get metrics, debugging, and more. It's lightweight and small enough for this installation make sense.
Try it. You might just like it :)
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”.
[1] https://blog.linkerd.io/2018/09/18/announcing-linkerd-2-0/
Earlier quoted context omitted.
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.
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)
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.
I’ll keep an eye on it for possible future day where it supports bare OS.