Introducing Conduit – open-source service mesh for Kubernetes

Re:Introducing Conduit – open-source service mesh for Kubern... by maktouch on Tuesday December 05, 2017 @02:25PM (#15854880)

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!

[ Parent | on HN ]

Re:Introducing Conduit – open-source service mesh for Kubern... by manigandham on Tuesday December 05, 2017 @03:43PM (#15855689)

If you just want Ingress with Envoy, Heptio now has the Contour project:

https://github.com/heptio/contour

[ Parent | on HN ]

Re:Introducing Conduit – open-source service mesh for Kubern... by olix0r on Tuesday December 05, 2017 @02:48PM (#15855133)

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)!

[ Parent | on HN ]

Re:Introducing Conduit – open-source service mesh for Kubern... by politician on Tuesday December 05, 2017 @02:56PM (#15855213)

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").

[ Parent | on HN ]