Considering that both use Envoy as a proxy, is Contour an alternative to Istio https://istio.io/ ?
Istio is for building a service mesh inside your network of microservices. This is about the front facing ingress to get into your services from the internet. It's closer to Ambassador (https://getambassador.io)
Ambassador is positioned as API GW instead of ingress controller. Contour is designed to be an ingress controller.
Istio comes with its own ingress controller that uses envoy.
This is an alternative to ambassador, as already said, or nginx-ingress.
Ambassador is positioned as API GW instead of ingress controller. Contour is designed to be an ingress controller.
API GW also acts as ingress controller but has more features than ingress controller to manage the APIs.
Contour is comparable to Istio-ingress, nginx ingress controller or HAProxy ingress controller.
Istio provides a control plane and can be deployed to also provide you with a service mesh with a side car approach. Istio also gives you features like rate limiting, traffic shaping, authentication (tls mutual auth) and metrics out of the box. Contour is meant to solve the ingress problem by using Envoy as a reverse proxy. I think it will primarily be focused on doing that.
Why would I use this over the batters included Nginx Ingress controller?
No SSL/TLS termination should be a deal breaker right off.
Initially thought this might be something to do with https://www.ingress.com/ and wondered how it could be played with a controller ...
When linking to GitHub, please link to the readme. Without knowing anything about the project, that's what we'll read first, and the additional click needed in mobile is a waste.