The ingress concept in Kubernetes is about controlling access to your services and potentially providing additional features, such as the following:
- SSL termination
- Authentication
- Routing to multiple services
There is an ingress resource that defines routing rules for other relevant information, and there is also an ingress controller that reads all the ingress resources defined in the cluster (across all namespaces). The ingress resource receives all the requests and routes to the target services that distribute them to the backing pods. The ingress controller serves as a cluster-wide software load balancer and router. Often, there will be a hardware load balancer that sits in front of the cluster and sends all traffic to the ingress controller.
Let's go ahead and put all of these concepts together and expose Delinkcious to the...
