Ingress in k8s its a way to expose our pods and deployment outside the cluster. In constrast with load balancer and NodePort services the Ingress is able to also handle TLS certificates, DDoS protection, route handling, load balancing based on request information and much more.
The ingress solutions are provided by the Controllers, which has many players, one of the most famour is the Nginx Ingress Controller, but there are many more, enterprise solutions, Cloud-Based products, etc.
It's also good to point out that the Ingress is a predecessor of the Gateway API object in k8s, a new way to expose the deployments outside the cluster provided by the K8S team itself. Its the recommended way today to expose the services.
- Nginx Ingress Controller
- Traefik
- HAProxy
- Istio
Contexts are used to navigate between clusters, it messes with the kube config files. There are cmd shell plugins to tell on which k8s cluster your are at the moment so you don't deploy objects at the wrong cluster.
To setup Kind (Kubernetes in Docker) with Ingress follow their documentation at https://kind.sigs.k8s.io/docs/user/ingress/