RouteTable

Proto: route_table.proto

Package: networking.gloo.solo.io

Types:

• DelegateAction

• DirectResponseAction

• ForwardToAction

• GraphQLAction

• GraphQLAction.Options

• HTTPRoute

• HTTPRoute.LabelsEntry

• RedirectAction

• RouteTableSpec

• RouteTableStatus

• RouteTableStatus.AppliedRoutePoliciesEntry

• RouteTableStatus.WorkspacesEntry

• DelegateAction.SortMethod

• RedirectAction.RedirectResponseCode

DelegateAction

DirectResponseAction

ForwardToAction

when a route is matched, forward the request to the destinations specified in this action

GraphQLAction

GraphQLAction.Options

HTTPRoute

An HTTP route pairs a set of HTTP Request Matchers with an action to take when a request is matched. HTTP Routes can be named and labeled for the purpose of metrics and applying policies.

HTTPRoute.LabelsEntry

RedirectAction

RouteTableSpec

RouteTables defines one or more hosts and a set of traffic route rules to handle traffic for these hosts. The traffic route rules can be delegated to other RouteTable based on one or more given hosts or specific paths.

You may deploy a RouteTable resource in any namespace within your workspace. In order for the RouteTable to be used outside of your workspace, you must deploy the RouteTable resource in the root config of your workspace and label it with workspace.solo.io/exported: "true". If your RouteTable delegates some traffic rules to another RouteTable, the delegated RouteTable may reside in the same workspace or different workspace from your RouteTable. If they are in different workspaces, the delegated RouteTable must reside in the root config of their workspaces and labelled with workspace.solo.io/exported: "true".

RouteTable can be used to match traffic originating from a gateway as well as from sidecars within the mesh, depends on the configuration of the virtualGateways field.

The following example defines route configuration for the ‘uk.bookinfo.com’ and ‘eu.bookinfo.com’ hosts, when traffic arriving at the my-gateway virtual gateway which is declared in the my-gateway-ws workspace. When the cookie in the header matches to ‘user=dev-123’, traffic is forwarded to the port 7777 of the v1 of reviews.qa. When the path matches exactly to /reviews/, 80% traffic is forwarded to the port 9080 of reviews.prod and 20% traffic is forwarded to the port 9080 of reviews.qa. All other traffic is sent to the default destination, which is the port 9080 of reviews.prod service in the bookinfo workspace.

apiVersion: networking.gloo.solo.io/v2
kind: RouteTable
metadata:
  name: bookinfo-root-routes
  namespace: bookinfo
spec:
  hosts:
    - 'uk.bookinfo.com'
    - 'eu.bookinfo.com'
  virtualGateways:
    - name: my-gateway
      namespace: my-gateway-ws
  defaultDestination:
    ref:
      name: reviews
      namespace: prod
    port:
      number: 9080
  http:
    - name: reviews-qa
      matchers:
        - headers:
            - name: cookie
              value: 'user=dev-123'
      forwardTo:
        destinations:
          - ref:
              name: reviews
              namespace: qa
            subset: 
              version: v1
            port:
              number: 7777
    - name: reviews
      matchers:
        - name: review-prefix
          uri:
            exact: /reviews/
      forwardTo:
        destinations:
          - weight: 80
          - ref:
              name: reviews
              namespace: qa
            port:
              number: 9080
            weight: 20

The following example defines route configuration for the ‘uk.bookinfo.com’ and ‘eu.bookinfo.com’ hosts, when traffic arriving at the my-gateway virtual gateway which is declared in the my-gateway-ws workspace. When the path matches prefix /lambda, traffic is forwarded to the backing aws-provider CloudProvider, where There is an associated CloudResources resource containing a lambda service named logicalName aws-dest within it. An option, “SYNC”, is also passed to indicate we want to route to the backing cloud function synchronously (though in this case, “SYNC” is the default option and can be safely omitted).

apiVersion: networking.gloo.solo.io/v2
kind: RouteTable
metadata:
  name: bookinfo-root-routes
  namespace: bookinfo
spec:
  hosts:
    - 'uk.bookinfo.com'
    - 'eu.bookinfo.com'
  virtualGateways:
    - name: my-gateway
      namespace: my-gateway-ws
  defaultDestination:
    ref:
      name: reviews
      namespace: prod
    port:
      number: 9080
  http:
    - name: lambda
      matchers:
        - uri:
            prefix: /lambda
      labels:
        route: lambda
      forwardTo:
        destinations:
          - ref:
              name: aws-provider
              namespace: bookinfo
              cluster: cluster-1
            kind: CLOUD_PROVIDER
            function:
              logicalName: aws-dest
              awsLambda:
                invocationStyle: SYNC

The following example defines route configuration for the ‘uk.bookinfo.com’ and ‘eu.bookinfo.com’ hosts, when traffic arriving at the my-gateway virtual gateway which is declared in the my-gateway-ws workspace. When the path matches prefix /lambda, traffic is forwarded to the delegated routetable for handling lambdas. allowedRoutes is included to restrict usage of CloudProvider functionality which routes to cloud functions backend-function-* in region us-east-2 and which assume the dev-team-B-* IAM role.

apiVersion: networking.gloo.solo.io/v2
kind: RouteTable
metadata:
  name: bookinfo-root-routes
  namespace: bookinfo
spec:
  hosts:
    - 'uk.bookinfo.com'
    - 'eu.bookinfo.com'
  virtualGateways:
    - name: my-gateway
      namespace: my-gateway-ws
  defaultDestination:
    ref:
      name: reviews
      namespace: prod
    port:
      number: 9080
  http:
    - name: lambda
      matchers:
        - uri:
            prefix: /lambda
      labels:
        route: lambda
      delegate:
        allowedRoutes:
          - cloudProvider:
              aws:
                lambda_function:
                  - backend-function-.*
                iam_roles:
                  - dev-team-B-.*
                regions:
                  - us-east-2
        routeTables:
          - labels:
              table: lambda

RouteTableStatus

reflects the status of the RouteTable

RouteTableStatus.AppliedRoutePoliciesEntry

RouteTableStatus.WorkspacesEntry

DelegateAction.SortMethod

RedirectAction.RedirectResponseCode