@annotations @route.header @router.cookie @release-1.22

Feature: Priority rules

An Ingress may define routing rules based on the request path. If the HTTP request path matches the paths and cookie info in the Ingress objects, the traffic is routed to its backend service.

Scenarios

Status	Progress
Passed	100.00%
Failed	0.00%

Scenario: An Ingress with path rules and cookie should send traffic to the matching backend service

(exact /, cookie, header matches request / with cookie and header)

Given 10s an Ingress resource in a new random namespace +Show Parameter


              apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: same-host-same-path-num-diff
  annotations:
    bfe.ingress.kubernetes.io/router.cookie: "uid:abcd"
    bfe.ingress.kubernetes.io/router.header: "h_key:h_value"
spec:
  rules:
    - host: "same-host-same-path-num-diff"
      http:
        paths:
          - path: /
            pathType: Exact
            backend:
              service:
                name: service-match-2
                port:
                  number: 3000

And 5s an Ingress resource in a new random namespace +Show Parameter


              apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: same-host-same-path-num-diff
  annotations:
    bfe.ingress.kubernetes.io/router.cookie: "uid:abcd"
spec:
  rules:
    - host: "same-host-same-path-num-diff"
      http:
        paths:
          - path: /
            pathType: Exact
            backend:
              service:
                name: service-match-1
                port:
                  number: 3000

And 6s The Ingress status shows the IP address or FQDN where it is exposed

When 0s I send a GET request to http://same-host-same-path-num-diff/ with header +Show Parameter


              {"Cookie": ["uid=abcd"],"h_key": ["h_value"]}

Then 0s the response status-code must be 200

And 0s the response must be served by the service-match 2 service

Duration: 21s

Scenario: An Ingress with path rules and cookie should send traffic to the matching backend service

(exact /, cookie matches request / with cookie)

Given 5s an Ingress resource in a new random namespace +Show Parameter


              apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: same-host-same-path-num-diff
  annotations:
    bfe.ingress.kubernetes.io/router.cookie: "uid:abcd"
    bfe.ingress.kubernetes.io/router.header: "h_key:h_value"
spec:
  rules:
    - host: "same-host-same-path-num-diff"
      http:
        paths:
          - path: /
            pathType: ImplementationSpecific
            backend:
              service:
                name: service-match-2
                port:
                  number: 3000

And 5s an Ingress resource in a new random namespace +Show Parameter


              apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: same-host-same-path-num-diff
  annotations:
    bfe.ingress.kubernetes.io/router.cookie: "uid:abcd"
spec:
  rules:
    - host: "same-host-same-path-num-diff"
      http:
        paths:
          - path: /
            pathType: ImplementationSpecific
            backend:
              service:
                name: service-match-1
                port:
                  number: 3000

And 6s The Ingress status shows the IP address or FQDN where it is exposed

When 0s I send a GET request to http://same-host-same-path-num-diff/ with header +Show Parameter


              {"Cookie": ["uid=abcd"]}

Then 0s the response status-code must be 200

And 0s the response must be served by the service-match 1 service

Duration: 16s

Scenario: An Ingress with path rules and cookie should send traffic to the matching backend service

(exact /, cookie matches request / with cookie)

Given 5s an Ingress resource in a new random namespace +Show Parameter


              apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: same-host-same-path-num-diff
  annotations:
    bfe.ingress.kubernetes.io/router.cookie: "uid:abcd"
    bfe.ingress.kubernetes.io/router.header: "h_key:h_value"
spec:
  rules:
    - host: "same-host-same-path-num-diff"
      http:
        paths:
          - path: /
            pathType: ImplementationSpecific
            backend:
              service:
                name: service-match-2
                port:
                  number: 3000

And 10s an Ingress resource in a new random namespace +Show Parameter


              apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: same-host-same-path-num-diff
  annotations:
    bfe.ingress.kubernetes.io/router.header: "h_key:h_value"
spec:
  rules:
    - host: "same-host-same-path-num-diff"
      http:
        paths:
          - path: /
            pathType: ImplementationSpecific
            backend:
              service:
                name: service-match-1
                port:
                  number: 3000

And 6s The Ingress status shows the IP address or FQDN where it is exposed

When 0s I send a GET request to http://same-host-same-path-num-diff/ with header +Show Parameter


              {"h_key": ["h_value"]}

Then 0s the response status-code must be 200

And 0s the response must be served by the service-match 1 service

Duration: 21s

Scenario: An Ingress with path rules and cookie should send traffic to the matching backend service

(exact /, cookie matches request / with cookie)

Given 5s an Ingress resource in a new random namespace +Show Parameter


              apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: same-host-same-path-num-same
  annotations:
    bfe.ingress.kubernetes.io/router.cookie: "uid:abcd"
spec:
  rules:
    - host: "same-host-same-path-num-same"
      http:
        paths:
          - path: /
            pathType: ImplementationSpecific
            backend:
              service:
                name: service-match-2
                port:
                  number: 3000

And 10s an Ingress resource in a new random namespace +Show Parameter


              apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: same-host-same-path-num-same1
  annotations:
    bfe.ingress.kubernetes.io/router.header: "h_key:h_value"
spec:
  rules:
    - host: "same-host-same-path-num-same"
      http:
        paths:
          - path: /
            pathType: ImplementationSpecific
            backend:
              service:
                name: service-match-1
                port:
                  number: 3000

And 3s The Ingress status shows the IP address or FQDN where it is exposed

When 0s I send a GET request to http://same-host-same-path-num-same/ with header +Show Parameter


              {"Cookie": ["uid=abcd"],"h_key": ["h_value"]}

Then 0s the response status-code must be 200

And 0s the response must be served by the service-match 2 service

Duration: 18s

BFE ingress controller e2e test