An Ingress object does nothing on its own. An Ingress controller is the component that watches Ingress resources through the API and configures a reverse proxy to route traffic accordingly. Kubernetes does not ship a controller in its core; the cluster needs one installed. If none is running, Ingresses are accepted but no traffic is routed, and the ADDRESS column of kubectl get ingress stays empty.
Keep reading for free
Create a free StudyToCert account to read the rest of this lesson: 6 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.