Ingress can manage external access to Services in a Kubernetes cluster, typically using HTTP or HTTPS. For example, it can route traffic to the underlying Services based on URL paths or HTTP headers such as the hostname. Instead of exposing a number of Services externally, either using node ports or through load balancers, it is, in general, more convenient to set up an Ingress in front of the Services. To handle the actual communication defined by the Ingress objects, an Ingress controller must be running in the cluster

Introduction:

1. An API object that manages external access to the services in a cluster

2. typically it works on http request

3. Ingress may provide load balancing, SSL termination and name-based virtual hosting

4. Ingress exposes HTTP and HTTPS routes from outside the cluster to services within the cluster.

5. Traffic routing is controlled by rules defined on the Ingress resource.

An Ingress may be configured to give Services externally-reachable URLs, load balance traffic, terminate SSL /

TLS, and offer name-based virtual hosting

6.

usually ingress provide a load balancer, though it may also configure your edge router or additional

frontends to help handle the traffic

7.

8. An Ingress does not expose arbitrary ports or protocols.

Exposing services other than HTTP and HTTPS to the internet typically uses a service of

type Service.Type=NodePort or Service.Type=LoadBalancer

9.

10. Ingress mostly apply on service so we can say that it's high level object of service.