An Ingress is an API object describing HTTP and HTTPS routing from outside the cluster to Services, by hostname and path. On its own it does nothing. An Ingress controller, a reverse proxy such as an NGINX-, HAProxy- or Traefik-based controller running as Pods, watches Ingress objects and configures itself to match. Kubernetes does not ship one, so installing a controller (usually with Helm) is step one. The controller itself is exposed with a NodePort or LoadBalancer Service.
Free account
Keep reading for free
Create a free StudyToCert account to read the rest of this lesson: 5 more sections, 4 key terms, a real-world example, an exam tip and self-check questions. Every lesson, lab and practice test is free with an account.