Question

You deploy an Ingress resource named 'web-ingress' in the 'shop' namespace to route external traffic to a ClusterIP Service. The Service has healthy endpoints and is reachable from inside the cluster. However, after several minutes, 'kubectl get ingress web-ingress -n shop' shows an empty ADDRESS field, and no external traffic reaches the application. What is the most likely cause?

Accepted Answer

No Ingress controller is running (or the Ingress does not reference a matching ingressClassName), so nothing is programming the routing rules or assigning an address.

Answer

The backing Service must be of type NodePort or LoadBalancer; an Ingress cannot forward traffic to a ClusterIP Service.

Answer

CoreDNS has not created a DNS record for the Ingress hostname, so the ADDRESS field remains empty until DNS propagates.

Answer

A default-deny NetworkPolicy in the 'shop' namespace is blocking the controller from populating the Ingress status.