-  path : /cluster-status backend : serviceName : cluster-status servicePort : 80 Dedicated rules for the Ingress controller for dispatching requests based on the request path Redirect every request to Service  random-generator … … except  /cluster-status  which goes to another Service Since every Ingress controller implementation is different, apart from the usual Ingress definition, a controller may require additional configuration, which is passed through annotations. Assuming the Ingress is configured correctly, the preceding def‐ inition would provision a load balancer and get an external IP address that services two Services under two different paths, as shown in Figure 12-7. Ingress is the most powerful and at the same time most complex  Service Discovery mechanism on Kubernetes. It is most useful for exposing multiple services under the same IP address and when all services use the same L7 (typically HTTP) protocol. Figure 12-7. Application layer service discovery 112  |  Chapter 12: Service Discovery