• Ingress Controller allows inbound connections to cluster

• It's an alternative to external Loadbalancer and nodePorts

• Ingress makes it simple to provide services that need a connection from outside the cluster.

• With ingress, you may run your own ingress controller, which is essentially a loadbalancer within the Kubernetes cluster. If you don't want to use the default one, you may write your own.

• Assume you've set up an ingress controller, and when you try to access it, the request is sent to the ingress controller on the pod. The ingress controller then uses the rules stored on the ingress controller to direct traffic to the appropriate pods.

Ingress rules:
example1.com => pod 1
example2.com => pod 2