Creating Ingress resources based on domains

We'll try to refactor our devops-toolkit Ingress definition so that the Controller forwards requests coming from the devopstoolkitseries.com domain. The change should be minimal, so we'll get down to it right away.

cat ingress/devops-toolkit-dom.yml  

When compared with the previous definition, the only difference is in the additional entry host: devopstoolkitseries.com. Since that will be the only application accessible through that domain, we also removed the path: / entry.

Let's apply the new definition:

kubectl apply \
  -f ingress/devops-toolkit-dom.yml \
  --record  

What would happen if we send a similar domain-less request to the Application? I'm sure you already know the answer, but we'll check it out anyways:

curl -I "http://$IP"  

The output is as follows:

HTTP/1.1 404 Not Found
Server: nginx...