HTTPProxy wildcard route priorities

[stasmir]

Hi all,

The question is how to determine priority for wildcard routes defined for HTTPProxy.
For example, there are three paths:

1. /api/data-stores
2. /api/data-stores/@dataStoreId/data-sets
3. /api/data-stores/@dataStoreId/data-sets/@dataSetId/versions
4. and all other paths

The intention is to define the following routes:

1. Requests by the following path prefix '/api/data-stores' should be routed to QueryService
2. Requests by the following path prefix '/api/data-stores/*/data-sets' should be routed to QueryService
3. Requests by the following path prefix '/api/data-stores//data-sets//versions' should be routed to CommandService
4. Requests by other paths should be routed to UIService

So, could you please advise on how can I achieve the desired behavior?
In this case
GET /api/data-stores should be routed to QueryService
GET /api/data-stores/123/data-sets should be routed to QueryService too
POST /api/data-stores/123/data-sets/456/versions should be routed to CommandService
GET /ui should be routed to UIService

apiVersion: projectcontour.io/v1
kind: HTTPProxy
metadata:
  name: ingress-route-prod-main
  namespace: 123
  annotations:
    projectcontour.io/ingress.class: contour
  labels:
    cluster: prod
spec:
  routes:
    - services:
        - name: QueryService
          port: 80
      conditions:
        - prefix: /api/data-stores  # this route will have the highest priority and below routes will be ignored. But what priority will be if the prefix is /api/data*stores

    - services:
      - name: QueryService
        port: 80
      conditions:
        - prefix: /api/data-stores/*/data-sets

    - services:
      - name: CommandService
        port: 80
      conditions:
        - prefix: /api/data-stores/*/data-sets/*/versions

    - services:
      - name: UIService
        port: 80
      conditions:
        - prefix: /

[stasmir]

Currently, with the above configuration requests:
GET /api/data-stores
GET /api/data-stores/123/data-sets
POST /api/data-stores/123/data-sets/456/versions
all routed to QueryService

If I change the first route with the prefix /api/data*stores then all requests are routed to UIService

Any ideas how should I reorder routes to get desired behavior?

[sunjayBhatia]

At the moment contour does not support globbing or regexes in prefix matches on an HTTPProxy due to inclusion rules and possible routing ambiguity, see this issue for some context: #1179

The matches you have written are taken literally and globbing is not considered, so you would need a request with a path prefix that contains the literal character * in it to match the routes you've configured

In general, longer path prefixes are ordered first when sent to Envoy, so e.g. /foo/bar will "win" over a route with match for /foo given a request with path /foo/bar/baz

[stasmir]

Is it possible to create a route based on HTTP verb, like route all GET to one service and other POST, PUT, etc to another service?

[sunjayBhatia]

see #4999 (comment)