Introducing Conduit – open-source service mesh for Kubernetes • Hacker News Board

Introducing Conduit – open-source service mesh for Kubernetes

#1

Post by steveklabnik » Tue, Dec 05, 2017, 4:12 PM UTC

Introducing Conduit – open-source service mesh for Kubernetes
buoyant.io

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

#2

Post by Lukesys » Tue, Dec 05, 2017, 4:22 PM UTC

Please don't release a toolbar ;)

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

#3

Post by csears » Tue, Dec 05, 2017, 4:27 PM UTC

How does this compare to Istio or Envoy?

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

#4

Post by juandazapata » Tue, Dec 05, 2017, 4:27 PM UTC

There's a company named Conduit. Possibly incurring into trademark violations.

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

#5

Post by gechr » Tue, Dec 05, 2017, 4:29 PM UTC

At first glance, this looks like a direct competitor to Envoy[1].

I'm sure the documentation will improve as the product matures, but right now much is left to the imagination.

Could you perhaps go in to more detail on the differences between the two?

[1] https://www.envoyproxy.io/

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

#6

Post by thunderman10 » Tue, Dec 05, 2017, 4:30 PM UTC

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

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

#7

Post by SEJeff » Tue, Dec 05, 2017, 4:33 PM UTC

I'm genuinely surprised they don't make a comparison to envoy or istio given the users they're attempting to target.

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

#8

Post by Operyl » Tue, Dec 05, 2017, 4:50 PM UTC

thunderman10 wrote: post #6

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

Why? Conduit seems as good a name as any for a project like this, if you ask me. Am I missing something here?

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

#9

Post by olix0r » Tue, Dec 05, 2017, 4:50 PM UTC

gechr wrote: post #5

At first glance, this looks like a direct competitor to Envoy[1]. I'm sure the documentation will improve as the product matures, but right now much is left to the imagination. Could you perhaps go in to more detail on the differences between the two? [1] https://www.envoyproxy.io/

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.

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

#10

Post by olix0r » Tue, Dec 05, 2017, 4:55 PM UTC

csears wrote: post #3

How does this compare to Istio or Envoy?

Conduit will probably have quite a bit of feature-overlap with Istio, especially, as it matures.

However, I think you'll find that the projects will be quite different in the way that they prioritize features and operate.

Our goals for Conduit are to provide a minimal, production-ready, commercially-supportable service mesh in the near-term. Time will tell how each projects goals and constraints lead to different user experiences.