Which statement is true about Ingress in Kubernetes in relation to the routing of traffic?

• A. Ingress routes external HTTP and HTTPS traffic to services within the cluster
• B. Ingress handles internal TCP traffic only
• C. Ingress automatically creates external load balancers for all services
• D. Ingress bypasses the need for DNS

Answer: (A)

The essence of what Ingress does is to expose HTTP/HTTPS routes from outside the cluster and route them to the appropriate services inside the cluster using host and path rules. An Ingress resource defines how external requests should be directed, and an Ingress Controller enforces those rules at the edge of the cluster, typically using a cloud load balancer or similar edge proxy. This is why the statement about Ingress routing external HTTP and HTTPS traffic to internal services is true.

Keep in mind that Ingress is not focused on internal TCP traffic by default, and while some controllers can extend functionality to TCP/UDP, the standard use case is HTTP(S) routing. It also doesn’t automatically create a separate external load balancer for every service; rather, a single Ingress Controller, exposed by an external endpoint, handles many routes. DNS still plays a role because you map your domain names to the Ingress Controller’s external IP or hostname to reach the exposed services.