Creating an Ingress resource with default backends

In some cases, we might want to define a default backend. We might want to forward requests that do not match any of the Ingress rules.

Let's take a look at an example:

curl -I -H "Host: acme.com" \
    "http://$IP"

So far, we have two sets of Ingress rules in our cluster. One accepts all requests with the base path /demo. The other forwards all requests coming from the devopstoolkitseries.com domain. The request we just sent does not match either of those rules, so the response was once again 404 Not Found.

Let's imagine that it would be a good idea to forward all requests with the wrong domain to the devops-toolkit application. Of course, by "wrong domain", I mean one of the domains we own, and not one of those that are already included in Ingress rules:

cat ingress/default-backend.yml...