Ingress resources help us to publish applications deployed on Kubernetes clusters. They work very well with HTTP and HTTPS services, providing many features for distributing and managing traffic between services. This traffic will be located on the OSI model's transport and application layers; they are also known as layers 4 and 7, respectively. It also works with raw TCP and UDP services; however, in these cases, traffic will be load balanced at layer 4 only.
These resources route traffic from outside the cluster to services running within the cluster. Ingress resources require the existence of a special service called an ingress controller. These services will load balance or route traffic using rules created by ingress resources. Therefore, publishing an application using this feature requires two components:
- Ingress resource: The rules to apply to incoming traffic
- Ingress controller: The load balancer that will automatically convert or translate ingress...
