Question

You deployed an NGINX Ingress controller in a bare-metal cluster. The controller Pods are Running, and an Ingress resource with a valid IngressClass points to a backend Service that has healthy endpoints. External clients on the corporate network can reach worker nodes directly by IP, but there is no cloud load balancer available. You want external HTTP traffic to reach the Ingress controller reliably through any node. Which configuration of the Ingress controller's own Service enables this in a bare-metal environment without a cloud provider?

Accepted Answer

Expose the Ingress controller with a Service of type NodePort (or a LoadBalancer backed by MetalLB), so external clients can reach the controller on a node IP and the request is then routed by the Ingress rules.

Answer

Expose the Ingress controller with a Service of type ClusterIP, since the Ingress resource already provides the external entry point independent of the controller's Service.

Answer

Delete the Ingress controller's Service entirely; the Ingress resource binds directly to node ports automatically once an IngressClass is set.

Answer

Create a headless Service (clusterIP: None) for the Ingress controller so DNS returns the Pod IPs directly to external clients.