News for hackers. Stuff that matters.

A comment on Introducing Conduit – open-source service mesh for Kubernetes. Parent comment

Re:Introducing Conduit – open-source service mesh for Kubern... by olix0r on Tuesday December 05, 2017 @11:50AM (#15852994)
Like Linkerd, Envoy is a proxy that can be used used to build a service mesh. Conduit is a service mesh that includes a proxy.

So, yes, Conduit uses something that competes with Envoy ;) But I would not say that Conduit and Envoy are equivalent things.

[ Parent | on HN ]
Re:Introducing Conduit – open-source service mesh for Kubern... by gmiranda23 on Tuesday December 05, 2017 @12:16PM (#15853289)
A service mesh needs a data plane (e.g. Envoy) and a control plane (e.g. Istio). Conduit has both in one product.
[ Parent | on HN ]
Re:Introducing Conduit – open-source service mesh for Kubern... by politician on Tuesday December 05, 2017 @02:54PM (#15855185)
Istio runs on Envoy; I'm not sure how Conduit is different from Istio.

https://istio.io/docs/concepts/traffic-management/load-balan...

[ Parent | on HN ]
Re:Introducing Conduit – open-source service mesh for Kubern... by otterley on Tuesday December 05, 2017 @05:14PM (#15856544)
But how is Conduit better than the combined products? Doing two things poorly is worse than doing one thing well. (I'm not suggesting that Conduit does anything poorly, but it's not clear how it's superior in any way to any competing implementation.)
[ Parent | on HN ]
Re:Introducing Conduit – open-source service mesh for Kubern... by tybit on Tuesday December 05, 2017 @09:53PM (#15858115)
What they are presumably going for is ease of use, Istio uses a pluggable service mesh with Envoy being the most common one, and Linkerd being one of the alternatives.

I'm guessing they think Conduit can bring value by being an intergated solution out of the box, and I'm excited to see if they can deliver on that.

[ Parent | on HN ]