Consul Connect/Mesh/Envoy features for reverse-proxy work?

Perhaps a dumb question, but as I have gone through my Hashi-Stack journey, I have played around with Fabio, Traefik, and good 'ole fashioned nginx as reverse-proxy options for routing to my various services. I haven’t made the leap to Consul-Connect yet, but as I watch these announcements roll in, and from what I understand about Envoy (which is not that much yet), it seems like if I were to migrate my services over to the Connect implementation patterns, that I might be able to have Envoy take over for my reverse-proxy / ingress routing that Traefik currently handles.

Is this a misread of what comes with Connect and the Envoy integrations? I get that there’s way more to it than that, I’m just trying to make sense of where to get a foothold and what would likely change in my home cluster before I venture down the path.

Thanks in advance,

1 Like

Hi @dehuszar,

Consul 1.8 introduced Ingress gateways which can potentially be used in the same role that Traefik provides, depending on what features you’re interested in. This does require the use of Consul service mesh.

See this blog post for info on what an Ingress gateway provides, and how to configure them on Kubernetes. Additional product documentation on Ingress can be found here

Hope this helps. Let me know if I can provide any additional detail.

I have the same issue with Ingress Gateway in Consul 1.8. Is there any reference architecture for internet public traffic into services in service mesh?

Currently I’m using Traefik + Consul Catalog for internet public traffic.