Gateway: An Abstract Resource Type for Routes

There is a proposal actually at the last Istio con around using Gateway to represent service mesh so that your routes do the same thing as a virtual service does. So one of the intentions for Gateway is to be kind of an abstract resource that doesn't really imply a direction. For ingress, it makes sense. These routes merge together and if this was NGINX, they would merge together to one NGINX config that configures your proxies. And these routes just end up configuring sidecar proxies because at the end of the day, when you look at the routing requirements or what you need to configure in a service mesh versus ingress there are very similar semantics.