@sig-network @conformance @release-1.19

Feature: Default backend

An Ingress with no rules sends all traffic to the single default backend. The default backend is part of the Ingress resource spec field `defaultBackend`. If none of the hosts or paths match the HTTP request in the Ingress objects, the traffic is routed to your default backend.

Scenarios

Status	Progress
Passed	100.00%
Failed	0.00%

Scenario Outline: An Ingress with no rules should send all requests to the default backend

Given 0s a new random namespace

Given 5s an Ingress resource named default-backend with this spec: +Show Parameter


              defaultBackend:
  service:
    name: echo-service
    port:
      number: 8080

Then 5s The Ingress status shows the IP address or FQDN where it is exposed

When 0s I send a GET request to http://my-host/

Then 0s the response status-code must be 200

And 0s the response must be served by the echo-service service

And 0s the response proto must be HTTP/1.1

And 0s the response headers must contain with matching

And 0s the request method must be GET

And 0s the request path must be

And 0s the request proto must be HTTP/1.1

And 0s the request headers must contain with matching

Duration: 10s

Scenario Outline: An Ingress with no rules should send all requests to the default backend

Given 0s a new random namespace

Given 5s an Ingress resource named default-backend with this spec: +Show Parameter


              defaultBackend:
  service:
    name: echo-service
    port:
      number: 8080

Then 5s The Ingress status shows the IP address or FQDN where it is exposed

When 0s I send a GET request to http://my-host/sub-path

Then 0s the response status-code must be 200

And 0s the response must be served by the echo-service service

And 0s the response proto must be HTTP/1.1

And 0s the response headers must contain with matching

And 0s the request method must be GET

And 0s the request path must be sub-path

And 0s the request proto must be HTTP/1.1

And 0s the request headers must contain with matching

Duration: 10s

Scenario Outline: An Ingress with no rules should send all requests to the default backend

Given 0s a new random namespace

Given 5s an Ingress resource named default-backend with this spec: +Show Parameter


              defaultBackend:
  service:
    name: echo-service
    port:
      number: 8080

Then 5s The Ingress status shows the IP address or FQDN where it is exposed

When 0s I send a POST request to http://some-host/

Then 0s the response status-code must be 200

And 0s the response must be served by the echo-service service

And 0s the response proto must be HTTP/1.1

And 0s the response headers must contain with matching

And 0s the request method must be POST

And 0s the request path must be

And 0s the request proto must be HTTP/1.1

And 0s the request headers must contain with matching

Duration: 10s

Scenario Outline: An Ingress with no rules should send all requests to the default backend

Given 0s a new random namespace

Given 5s an Ingress resource named default-backend with this spec: +Show Parameter


              defaultBackend:
  service:
    name: echo-service
    port:
      number: 8080

Then 5s The Ingress status shows the IP address or FQDN where it is exposed

When 0s I send a PUT request to http:///resource

Then 0s the response status-code must be 200

And 0s the response must be served by the echo-service service

And 0s the response proto must be HTTP/1.1

And 0s the response headers must contain with matching

And 0s the request method must be PUT

And 0s the request path must be resource

And 0s the request proto must be HTTP/1.1

And 0s the request headers must contain with matching

Duration: 10s

Scenario Outline: An Ingress with no rules should send all requests to the default backend

Given 0s a new random namespace

Given 5s an Ingress resource named default-backend with this spec: +Show Parameter


              defaultBackend:
  service:
    name: echo-service
    port:
      number: 8080

Then 5s The Ingress status shows the IP address or FQDN where it is exposed

When 0s I send a DELETE request to http://some-host/resource

Then 0s the response status-code must be 200

And 0s the response must be served by the echo-service service

And 0s the response proto must be HTTP/1.1

And 0s the response headers must contain with matching

And 0s the request method must be DELETE

And 0s the request path must be resource

And 0s the request proto must be HTTP/1.1

And 0s the request headers must contain with matching

Duration: 10s

Scenario Outline: An Ingress with no rules should send all requests to the default backend

Given 0s a new random namespace

Given 5s an Ingress resource named default-backend with this spec: +Show Parameter


              defaultBackend:
  service:
    name: echo-service
    port:
      number: 8080

Then 5s The Ingress status shows the IP address or FQDN where it is exposed

When 0s I send a PATCH request to http://my-host/resource

Then 0s the response status-code must be 200

And 0s the response must be served by the echo-service service

And 0s the response proto must be HTTP/1.1

And 0s the response headers must contain with matching

And 0s the request method must be PATCH

And 0s the request path must be resource

And 0s the request proto must be HTTP/1.1

And 0s the request headers must contain with matching

Duration: 10s

Kubernetes ingress controller conformance