Routing NG

[davecheney]

When IngressRoute was introduced a year ago (july 2018) we chose to only support prefix matching for routes. This was mostly a time to market decision, but also reflected the fact that we didn't know what other ways customers wanted to match routes on -- we knew that envoy also supported other methods, but without a signal from our userbase, blindly adding support for all of the existing mechanisms felt like throwing the problem over the wall to our users to figure out what worked best.

A year later there is clear signal that prefix routing is too limited. This is not a surprise. What is more interesting is customers want to route not just on prefix, substring, and regex -- the three we identified last year -- but also header matching, source ip, user agent, and many more.

This issue is a placeholder for a larger discussion about revising ingressroute's route matching. This will be part of, and intended to be delivered before Contour 1.0.

[davecheney]

Delivered in beta.1