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

Introducing Conduit – open-source service mesh for Kubernetes

buoyant.io

Post reply on HN
Print view View original

31–40 of 54 posts

Re: Introducing Conduit – open-source service mesh for Kubernetes

#31

Post by uean »

thunderman10 wrote: post #6

They should have chosen name that doesn`t immediately make users want to uninstall it.

I came here to say exactly this. A Google of "Conduit" gets every competing dictionary's take on the word. A search on "conduit software" gets you nothing but frustrated posts of people trying to remove conduit malware.

Re: Introducing Conduit – open-source service mesh for Kubernetes

#32

Post by uptown »

dsl wrote: post #14

But what in the hell is it? If your product is so revolutionary it defines a new market segment, you might want to bring the people with the money people up to speed.

This explanation was helpful to me: https://buoyant.io/2017/04/25/whats-a-service-mesh-and-why-d...

Re: Introducing Conduit – open-source service mesh for Kubernetes

#33

Post by treesloth »

dsl wrote: post #14

But what in the hell is it? If your product is so revolutionary it defines a new market segment, you might want to bring the people with the money people up to speed.

Had to google this myself, here's a link to their description of a service mesh.

https://buoyant.io/2017/04/25/whats-a-service-mesh-and-why-d...

Re: Introducing Conduit – open-source service mesh for Kubernetes

#36

Post by olix0r »

maktouch wrote: post #34

How does it work with ingress? Does it ship with its own ingress like istio? We tried istio a while back and it was too slow and hungry. Reverted back to no service mesh and it worked fine. I'm gonna be trying this next!

The first release doesn't include Ingress support. This is something we plan on folding into our Routing API in an upcoming release. If you have opinions on how you'd like to see Ingress implemented, now is a great time to share your thoughts (in a GitHub issue, is probably best)!

Re: Introducing Conduit – open-source service mesh for Kubernetes

#38

Post by politician »

gmiranda23 wrote: post #13
olix0r wrote: post #9

Earlier quoted context omitted.

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.

A service mesh needs a data plane (e.g. Envoy) and a control plane (e.g. Istio). Conduit has both in one product.

Istio runs on Envoy; I'm not sure how Conduit is different from Istio.

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

Re: Introducing Conduit – open-source service mesh for Kubernetes

#39

Post by politician »

maktouch wrote: post #34

How does it work with ingress? Does it ship with its own ingress like istio? We tried istio a while back and it was too slow and hungry. Reverted back to no service mesh and it worked fine. I'm gonna be trying this next!

Have you tried using envoy directly? That's what we run, and it works well. I'd be interested to hear about the kinds of problems you ran into (as in, "yikes, is there something we should be watching out for", not "marketing").
Post reply on HN