How to: Ingress rules
This is similar to defining API routes on a backend application, except each defined route points to a separate application/service/deployment.

- if no host is specified, the rule applies to all inbound HTTP traffic
- paths can be defined with a [POSIX regex](https://www.gnu.org/software/findutils/manual/html_node/find_html/)
- each path points to a resource backend defined with a `service.name` and a `service.port.name` or `service.port.number`posix_002dextended-regular-expression-syntax.html)
- both the host and path must match the content of an incoming request before the load balancer directs traffic to the referenced Service
- a default path `.spec.defaultBackend` can be defined on the Ingress or _Ingress controller_ for traffic that doesn't match any known paths, similar to a 404 route - if `defaultBackend` is not set, the default 404 behaviour will depend on the type of _Ingress controller_ in use