Kubernetes Service Meshes
Discussions compare a new service mesh or proxy tool to established options like Istio, Envoy, Linkerd, Ambassador, and Contour, focusing on features such as service discovery, load balancing, traffic management, and Kubernetes integration.
Activity Over Time
Top Contributors
Keywords
Sample Comments
This is a service mesh like Istio not an API gateway, it's mainly used for automatic and transparent service discovery and load balancing where client and server service endpoints don't have to worry about that, also other features are automatic handling of failure when one server endpoint isn't responding, traffic management, securing communications between services, enforcing L7/L4 kind of a firewall between services, telemetry, etc..., you probably don't want to use a
Maybe I'm misunderstanding the question, but you may want to have a look at Envoy: https://www.envoyproxy.io
Why wouldn’t you use istio or cilium for this?
thank you. As for #4, i've heard good things about https://istio.io - supposedly it does provide nice means to gain introspection to the traffic between services.
Have you tried Ambassador? Built on Envoy Proxy. We have submitted as well to the CNCF as an official project too. (Disclosure: I work on Ambassador).
If you're using Kubernetes, you should check out Ambassador. Declarative syntax, no database (persists to etcd), very high performance, built on Envoy Proxy.
have you tried Contour yet?https://projectcontour.io
How does this compare to Istio or Envoy?
So basically a sidecar, a service mesh :)
So many service meshes these days, how would this differ from Istio which seems to be the hot topic alongside Kubernetes?