This will create a load balancer forwarding all traffic to test-service service, unconditionally. The
loadbalancer ip can be found inside Status Field of the loadbalancer described response. If there are other
rules defined in Ingress then the loadbalancer will forward traffic to the test-service when no other rule is
matched.

Default Backend: An Ingress with no rules, like the one shown in the previous section, sends all
traffic to a single default backend. You can use the same technique to tell a loadbalancer
where to find your website’s 404 page, by specifying a set of rules and a default backend.
Traffic is routed to your default backend if none of the Hosts in your Ingress matches the Host in
request header, and/or none of the paths match url of request.

This Ingress will forward traffic to test-service if request comes from the host appscode.example.com only.
Other requests will be forwarded to default backend, default-service.

Default Backend also supports headerRules and rewriteRules.

Take your team where it needs to go.

Create your cluster in minutes. Our team is here to help and would be happy to chat with you.