@annotations @balance.weight @release-1.22

Feature: Load balance rules

Scenarios
Status Progress

Passed

 100.00%

Failed

 0.00%
Scenario: An Ingress with load balance rule 50-50 should send traffic to the matching backend service

(exact / and cookie matches request /)

check_circle
Given 10s an Ingress with service info whoami1:3000|whoami2:3000 resource in a new random namespace +Show Parameter 
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: balance-rules
  annotations:
    bfe.ingress.kubernetes.io/balance.weight: "{\"service\":{\"whoami1\":50, \"whoami2\":50}}"
spec:
  rules:
    - host: "balance-weight-50-50"
      http:
        paths:
          - path: /
            pathType: Exact
            backend:
              service:
                name: service
                port:
                  number: 3000
check_circle
And 6s The Ingress status shows the IP address or FQDN where it is exposed
check_circle
When 0s I send 100 GET requests to http://balance-weight 50 50/
check_circle
Then 0s the response status-code must be 200 the response body should contain the IP address of 2 different Kubernetes pods
check_circle
And 0s the response must be served by one of whoami1|whoami2 service
Duration: 16s query_builder
5
Scenario: An Ingress with load balance rule 1-1 should send traffic to the matching backend service

(exact / and cookie matches request /)

check_circle
Given 15s an Ingress with service info whoami1:3000|whoami2:3000 resource in a new random namespace +Show Parameter 
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: balance-rules
  annotations:
    bfe.ingress.kubernetes.io/balance.weight: "{\"service\":{\"whoami1\":1, \"whoami2\":1}}"
spec:
  rules:
    - host: "balance-weight-1-1"
      http:
        paths:
          - path: /
            pathType: Exact
            backend:
              service:
                name: service
                port:
                  number: 3000
check_circle
And 6s The Ingress status shows the IP address or FQDN where it is exposed
check_circle
When 0s I send 100 GET requests to http://balance-weight 1 1/
check_circle
Then 0s the response status-code must be 200 the response body should contain the IP address of 2 different Kubernetes pods
check_circle
And 0s the response must be served by one of whoami1|whoami2 service
Duration: 21s query_builder
5
Scenario: An Ingress with load balance rule 3-1 should send traffic to the matching backend service

(exact / and cookie matches request /)

check_circle
Given 15s an Ingress with service info whoami1:3000|whoami2:3000 resource in a new random namespace +Show Parameter 
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: balance-rules
  annotations:
    bfe.ingress.kubernetes.io/balance.weight: "{\"service\":{\"whoami1\":3, \"whoami2\":1}}"
spec:
  rules:
    - host: "balance-weight-3-1"
      http:
        paths:
          - path: /
            pathType: Exact
            backend:
              service:
                name: service
                port:
                  number: 3000
check_circle
And 6s The Ingress status shows the IP address or FQDN where it is exposed
check_circle
When 0s I send 100 GET requests to http://balance-weight 3 1/
check_circle
Then 0s the response status-code must be 200 the response body should contain the IP address of 2 different Kubernetes pods
check_circle
And 0s the response must be served by one of whoami1|whoami2 service
Duration: 21s query_builder
5
Scenario: An Ingress with load balance rule 1-1-1 should send traffic to the matching backend service

(exact / and cookie matches request /)

check_circle
Given 35s an Ingress with service info whoami1:3000|whoami2:3000|whoami3:3000 resource in a new random namespace +Show Parameter 
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: balance-rules
  annotations:
    bfe.ingress.kubernetes.io/balance.weight: "{\"service\":{\"whoami1\":1, \"whoami2\":1, \"whoami3\":1}}"
spec:
  rules:
    - host: "balance-weight-1-1-1"
      http:
        paths:
          - path: /
            pathType: Exact
            backend:
              service:
                name: service
                port:
                  number: 3000
check_circle
And 6s The Ingress status shows the IP address or FQDN where it is exposed
check_circle
When 0s I send 100 GET requests to http://balance-weight 1 1 1/
check_circle
Then 0s the response status-code must be 200 the response body should contain the IP address of 3 different Kubernetes pods
check_circle
And 0s the response must be served by one of whoami1|whoami2|whoami3 service
Duration: 41s query_builder
5
Scenario: An Ingress with load balance rule 200-177-121 should send traffic to the matching backend service

(exact / and cookie matches request /)

check_circle
Given 25s an Ingress with service info whoami1:3000|whoami2:3000|whoami3:3000 resource in a new random namespace +Show Parameter 
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: balance-rules
  annotations:
    bfe.ingress.kubernetes.io/balance.weight: "{\"service\":{\"whoami1\":200, \"whoami2\":177, \"whoami3\":121}}"
spec:
  rules:
    - host: "balance-weight-200-177-121"
      http:
        paths:
          - path: /
            pathType: Exact
            backend:
              service:
                name: service
                port:
                  number: 3000
check_circle
And 6s The Ingress status shows the IP address or FQDN where it is exposed
check_circle
When 0s I send 100 GET requests to http://balance-weight 200 177 121/
check_circle
Then 0s the response status-code must be 200 the response body should contain the IP address of 3 different Kubernetes pods
check_circle
And 0s the response must be served by one of whoami1|whoami2|whoami3 service
Duration: 31s query_builder
5
Scenario: An Ingress with load balance rule format error should not send traffic to the matching backend service

(exact / and cookie matches request /)

check_circle
Given 20s an Ingress with service info whoami1:3000|whoami2:3000 resource in a new random namespace +Show Parameter 
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: balance-rules
  annotations:
    bfe.ingress.kubernetes.io/balance.weight: "{\"service\":{\"whoami1\":50,, \"whoami2\":50}}"
spec:
  rules:
    - host: "balance-weight-50-50"
      http:
        paths:
          - path: /
            pathType: Exact
            backend:
              service:
                name: service
                port:
                  number: 3000
check_circle
And 3s The Ingress status should not be success
Duration: 23s query_builder
2
Scenario: An Ingress with load balance rule 0-0-0 should not send traffic to the matching backend service

(exact / and cookie matches request /)

check_circle
Given 25s an Ingress with service info whoami1:3000|whoami2:3000|whoami3:3000 resource in a new random namespace +Show Parameter 
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: balance-rules
  annotations:
    bfe.ingress.kubernetes.io/balance.weight: "{\"service\":{\"whoami1\":0, \"whoami2\":0, \"whoami3\":0}}"
spec:
  rules:
    - host: "balance-weight-0-0-0"
      http:
        paths:
          - path: /
            pathType: Exact
            backend:
              service:
                name: service
                port:
                  number: 3000
check_circle
And 3s The Ingress status should not be success
Duration: 28s query_builder
2
Scenario: An Ingress with load balance rule 1-1-(-1) should not send traffic to the matching backend service

(exact / and cookie matches request /)

check_circle
Given 30s an Ingress with service info whoami1:3000|whoami2:3000|whoami3:3000 resource in a new random namespace +Show Parameter 
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: balance-rules
  annotations:
    bfe.ingress.kubernetes.io/balance.weight: "{\"service\":{\"whoami1\":1, \"whoami2\":1, \"whoami3\":-1}}"
spec:
  rules:
    - host: "balance-weight-1-1-mimus-1"
      http:
        paths:
          - path: /
            pathType: Exact
            backend:
              service:
                name: service
                port:
                  number: 3000
check_circle
And 0s The Ingress status should not be success
Duration: 30s query_builder
2
Scenario: An Ingress with load balance rule 0.33-0.33-0.34 should not send traffic to the matching backend service

(exact / and cookie matches request /)

check_circle
Given 20s an Ingress with service info whoami1:3000|whoami2:3000|whoami3:3000 resource in a new random namespace +Show Parameter 
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: balance-rules
  annotations:
    bfe.ingress.kubernetes.io/balance.weight: "{\"service\":{\"whoami1\":0.33, \"whoami2\":0.33, \"whoami3\":0.34}}"
spec:
  rules:
    - host: "balance-weight-0.33-0.33-0.34"
      http:
        paths:
          - path: /
            pathType: Exact
            backend:
              service:
                name: service
                port:
                  number: 3000
check_circle
And 0s The Ingress status should not be success
Duration: 20s query_builder
2

BFE ingress controller e2e test